This topic has 4 replies, 2 voices, and was last updated 3 years, 6 months ago by 
-
Posts
-
Hi Team,
We are currently using Access Management 5.5 We have a requirement to create an alias unique identifier and password for user during creation. The users will be created using rest API call to AM 5.5 and the backend data store is Directory Server 5.5. The Rest API call will be triggered by a different Interface.
When the call is made to AM 5.5, it should create the user with submitted details and also set a alias identifier and password as per the policies defined and same needs to be returned to along with password as json response.
Any suggestions would be of great help.
If you are driving the creation of the user using the REST API, called from an app you control, then you can add in additional attributes (such as your alias) to the payload.
-Andy
@acorysmart421-com Thanks for the reply. Is it possible to generate the id dynamically in Directory Server when the rest API call is triggered without sending it as part of the payload. As per our requirement we don’t want to send the id and password in the payload but these attributes should be auto generated when the rest api call is triggered. Please let me know if there any features already available in AM 5.5.
Thanks,
Anirudh.Hi Anirudh
There is no out of the box feature to do this in AM. You aren’t using IDM for your identity management? AM isn’t as flexible as IDM as an identity management tool, but even in IDM your use-case would require customisation. Why can’t you send the id and password in the payload to AM? If an app you control is orchestrating the creation of users over the REST API, that would seem the easiest place to generate these automatically.
-Andy
You must be logged in to reply to this topic.
