AnsweredAssumed Answered

User creation and temporary password

Question asked by Max Tama on Oct 8, 2020
Latest reply on Oct 9, 2020 by Ahmed Nofal

Like • Show 0 Likes0
Comment • 5

Hello everybody.
At the moment, starting from reading a csv provided by HR, I am able to create an identity-user in IGL with the characteristics present in the file (name, surname, etc.).
What I would like to do is:

1. automatically create, when I collect a new user from HR file, an account also on AD (I have the connector), with userid that should be a "fixed_text" + "a number" that always increases automatically. For example: contoso-1, contoso-2, contoso-3 etc.
I tried to use naming convention, but I can't figure out how to manage a progressive number, avoiding using something already present.

2. I would like to set a temporary AD login password (generated by IGL) and send a link to a user; he should enter (somewhere :-) ) that password and then change it. How can I do? I can't figure out how to do it.

Can you suggest me how to do it? If you have screenshots even better!
thanks a lot

Max

Ahmed Nofal

Oct 9, 2020 9:56 PM

Correct Answer

Hi Max,

I believe Ian gave an adequate summary here. If you have further questions, please reach out to me on my mail address:

ahmed.nofal@rsa.com

See the reply in context

No one else had this question

Outcomes

Ahmed Nofal

Oct 8, 2020 12:21 PM

Hi Max,

Do you have an active PS project in place to discuss the use cases you mentioned here? If you do, I highly suggest engaging the project's RSA PS team on your points there.

These use cases (basically a joiner process) cannot be answered within a community question unfortunately.

Actions

Ian Staines

@ Ahmed Nofal on Oct 8, 2020 6:00 PM

Yes this forum is better place for specific questions on your implementation, not the best place to get a full solution.

You need to consider your Identity Data Collection separate from your provisioning process. They are linked (traditionally by provisioning rules) but they are separate processes.
You account creation is a separate process.
Your password policies and implementation are a separate process.

You need to consult with someone on your overall design before you commit to these steps as the choices you make now affect everything downstream.

Actions

Max Tama Oct 9, 2020 12:48 PM

I would like to understand the procedure for obtaining those two usecase, at least at high level.
I would like to study how to do it, so for this reason I asked to see some examples in this community, in order to test it in one of our labs

Hope someone can help here :-)

Thanks

Actions

Ian Staines

@ Max Tama on Oct 9, 2020 1:47 PM

At a high level.

You would create a Provisioning Joiner Rule to detect new users in your IDC. This Rule would generate provisioning either through a request form or through custom workflows. The Provisioning Form would use an Account Template to provision Entitlements to new users based on your requirements. The Account template would be associated with Pending Account parameters that were designed to work with your Connectors to provision Accounts automatically. Entitlement requires Account feature would be leveraged to create temporary Accounts for provisioning with AFX. The account names would be defined in the Naming Policies and Base Name Transforms and the password policies would be defined and configured in the password policies. Collectors would be designed to verify the new account and entitlement data. Workflows would be customized to ensure the approval and provisioning moved according to your business practices.

At a low level there are lots of decisions that need to be made on the details of these various solutions and how they interact with your infrastructure. In order to ensure success all of these considerations would have to be done in terms of your business practices.

Actions

Ahmed Nofal

@ Ian Staines on Oct 9, 2020 9:56 PM

Hi Max,

I believe Ian gave an adequate summary here. If you have further questions, please reach out to me on my mail address:

ahmed.nofal@rsa.com

1 person found this helpful

Actions

5 Replies

Ahmed Nofal Oct 8, 2020 12:21 PM
Mark Correct
Correct Answer
Hi Max,

Do you have an active PS project in place to discuss the use cases you mentioned here? If you do, I highly suggest engaging the project's RSA PS team on your points there.

These use cases (basically a joiner process) cannot be answered within a community question unfortunately.
Like • Show 1 Like1
Actions
- Ian Staines @ Ahmed Nofal on Oct 8, 2020 6:00 PM
  Mark Correct
  Correct Answer
  Yes this forum is better place for specific questions on your implementation, not the best place to get a full solution.
  
  You need to consider your Identity Data Collection separate from your provisioning process. They are linked (traditionally by provisioning rules) but they are separate processes.
  You account creation is a separate process.
  Your password policies and implementation are a separate process.
  
  You need to consult with someone on your overall design before you commit to these steps as the choices you make now affect everything downstream.
  Like • Show 0 Likes0
  Actions
Max Tama Oct 9, 2020 12:48 PM
Mark Correct
Correct Answer
I would like to understand the procedure for obtaining those two usecase, at least at high level.
I would like to study how to do it, so for this reason I asked to see some examples in this community, in order to test it in one of our labs
Hope someone can help here :-)
Thanks
Like • Show 0 Likes0
Actions
- Ian Staines @ Max Tama on Oct 9, 2020 1:47 PM
  Mark Correct
  Correct Answer
  At a high level.
  
  You would create a Provisioning Joiner Rule to detect new users in your IDC. This Rule would generate provisioning either through a request form or through custom workflows. The Provisioning Form would use an Account Template to provision Entitlements to new users based on your requirements. The Account template would be associated with Pending Account parameters that were designed to work with your Connectors to provision Accounts automatically. Entitlement requires Account feature would be leveraged to create temporary Accounts for provisioning with AFX. The account names would be defined in the Naming Policies and Base Name Transforms and the password policies would be defined and configured in the password policies. Collectors would be designed to verify the new account and entitlement data. Workflows would be customized to ensure the approval and provisioning moved according to your business practices.
  
  At a low level there are lots of decisions that need to be made on the details of these various solutions and how they interact with your infrastructure. In order to ensure success all of these considerations would have to be done in terms of your business practices.
  Like • Show 1 Like1
  Actions
  - Ahmed Nofal @ Ian Staines on Oct 9, 2020 9:56 PM
    Unmark Correct
    Correct Answer
    Hi Max,
    
    I believe Ian gave an adequate summary here. If you have further questions, please reach out to me on my mail address:
    ahmed.nofal@rsa.com
    1 person found this helpful
    Like • Show 2 Likes2
    Actions

User creation and temporary password

Outcomes

Related Content

Recommended Content