AnsweredAssumed Answered

RSA AM 8.5 not usable

Question asked by David Pala on Aug 21, 2020
Latest reply on Aug 21, 2020 by Jay Guillette

Like • Show 0 Likes0
Comment • 4

Hi Folks !

While qualifying & testing the new 8.5 release of RSA AM, I noticed something that seems to be a bug, and leading the Security Console not usable anymore for editing user accounts.

Why ?
Because there is no checkbox to "enable" the password authentication for a user.
Most problematic : the users are NOT configured with passwords in our deployment, so how could I now (in 8.5 version) make some renaming or adding comments, WITHOUT setting a password for the user ?! => IMPOSSIBLE

This is a MAJOR regression for us and leads RSA AM solution to be not usable anymore.

Kind Regards,

David

Jochen Klotz

Aug 21, 2020 6:25 AM

Correct Answer

Hi David, do you have the chance to check your Identity Source Settings in the operations console? Maybe the User Configuration switch does the trick.

Best Regards,

Jochen

See the reply in context

No one else had this question

Outcomes

Jochen Klotz

Aug 21, 2020 6:25 AM

Hi David, do you have the chance to check your Identity Source Settings in the operations console? Maybe the User Configuration switch does the trick.

Best Regards,

Jochen

2 people found this helpful

Actions

Edward Davis

@ Jochen Klotz on Aug 21, 2020 8:10 AM

Yes, this:

-Operations Console, Deployment Configuration, Identity Sources, Manage Existing--->

-perform a secondary login with a Security Console Admin name and password
-Select Internal Database dropdown, edit, and you'll land on the page Jochen shows

1 person found this helpful

Actions

David Pala Aug 21, 2020 8:33 AM

Jochen, Ed,

Many many thanks for pointing me THE trick so quickly ! (spent 4 days on the case I opened and still no answer from them :-))

I was not aware that anyone changed it here ; now I am...

I just updated the Identity Source as mentioned :

All is working perfectly now, and the checkbox for optional password is now here when creating a user :

I own you one guys ! :-)

Kind Regards,

David

Actions

Jay Guillette

@ David Pala on Aug 21, 2020 10:54 AM

It's because you used an Internal Database Identity Source. Obviously Authentication Manager is predominately about Tokens. Passwords might optionally be used in addition to a Token on an agent. The only place a password could be used by itself, without a token, would be on the AM Console; Security or Self-Service.

This is why the Security Console and Self Service Consoles each have Console Authentication setup, where you can choose (and/or) the RSA_Password for Internal DB user, or LDAP_Password for external Identity Source User in AD or Open LDAP etc...

Actions

4 Replies

Jochen Klotz Aug 21, 2020 6:25 AM
Unmark Correct
Correct Answer
Hi David, do you have the chance to check your Identity Source Settings in the operations console? Maybe the User Configuration switch does the trick.
Best Regards,
Jochen
2 people found this helpful
Like • Show 3 Likes3
Actions
- Edward Davis @ Jochen Klotz on Aug 21, 2020 8:10 AM
  Mark Correct
  Correct Answer
  Yes, this:
  
  -Operations Console, Deployment Configuration, Identity Sources, Manage Existing--->
  -perform a secondary login with a Security Console Admin name and password
  -Select Internal Database dropdown, edit, and you'll land on the page Jochen shows
  1 person found this helpful
  Like • Show 2 Likes2
  Actions
David Pala Aug 21, 2020 8:33 AM
Mark Correct
Correct Answer
Jochen, Ed,

Many many thanks for pointing me THE trick so quickly ! (spent 4 days on the case I opened and still no answer from them :-))
I was not aware that anyone changed it here ; now I am...

I just updated the Identity Source as mentioned :

All is working perfectly now, and the checkbox for optional password is now here when creating a user :

I own you one guys ! :-)

Kind Regards,
David
Like • Show 1 Like1
Actions
- Jay Guillette @ David Pala on Aug 21, 2020 10:54 AM
  Mark Correct
  Correct Answer
  It's because you used an Internal Database Identity Source. Obviously Authentication Manager is predominately about Tokens. Passwords might optionally be used in addition to a Token on an agent. The only place a password could be used by itself, without a token, would be on the AM Console; Security or Self-Service.
  
  This is why the Security Console and Self Service Consoles each have Console Authentication setup, where you can choose (and/or) the RSA_Password for Internal DB user, or LDAP_Password for external Identity Source User in AD or Open LDAP etc...
  Like • Show 1 Like1
  Actions

RSA AM 8.5 not usable

Outcomes

Related Content

Recommended Content