• State Not Answered
  • Replies 2 replies
  • Subscribers 65 subscribers
  • Views 76 views
  • Users 0 members are here
Options
Related

Importing/setting aliases for username

imkhonza
1 day ago

Hi All,

We have a situation where the IAM solution creates a username for the user/person, but the user then changes their surname, which is part of the username. We want to allow the user to have a new username based on the new surname but keep the old one so as not to create a new one or confuse the systems when a new user with the similar username criteria that makes the username joins the organization. 

So I am looking for a field in the IAM person record to map this and also to ensure we do not create duplicate/similar usernames that have been taken due to surname changes.

Example:
1 username: jdoe 

Marriages/Divorces:
2. username: jjones

I want to keep the jdoe and jjones linked to one person and also not allow another creation of jdoe or jjones.

Thanks

Kp

Parents
  • 0 1 day ago

    One suggestion I would have for this is to create a multi-valued-string Active Roles virtual attribute that could store the old user names (a.k.a. samaccountnames).

    You could call it something like edsvaPreviousSamAccount

    From a process flow perspective, I would suggest something like this:

    1. Active Roles Change Workflow detects a surname change
    2. Copies/appends the existing username (samaccountname) to the in process user's edsvaPreviousSamAccount virtual attribute
    3. New samaccountname gets constructed based on your rule.
    4. Some code checks all users' edsvaPreviousSamAccount virtual attributes for the existence of the new proposed samaccountname and if there are no dupe, the rename of the samaccountname is  allowed to proceed.

Reply
  • 0 1 day ago

    One suggestion I would have for this is to create a multi-valued-string Active Roles virtual attribute that could store the old user names (a.k.a. samaccountnames).

    You could call it something like edsvaPreviousSamAccount

    From a process flow perspective, I would suggest something like this:

    1. Active Roles Change Workflow detects a surname change
    2. Copies/appends the existing username (samaccountname) to the in process user's edsvaPreviousSamAccount virtual attribute
    3. New samaccountname gets constructed based on your rule.
    4. Some code checks all users' edsvaPreviousSamAccount virtual attributes for the existence of the new proposed samaccountname and if there are no dupe, the rename of the samaccountname is  allowed to proceed.

Children
No Data