yc954 (yc954) asked a question.
We have a scenario where a user is created in Okta with their mobile number as the username. Later, the user changes their mobile number and we need to update the username in Okta to reflect the new mobile number.
@yc954 (yc954)
Please check out this feature below. Not sure if you are aware of it . This may work for you . It lets user authenticate using alternate attributes. (This is not directly addressing changing username but may work for your use case)
https://help.okta.com/oie/en-us/content/topics/identity-engine/policies/multiple-identifiers.htm
HTH
-Bala
@yc954 (yc954) - So assuming the user is "Okta Sourced" && you mean they "update their Okta profile" with a new attribute and you then need to change their login to an alternate value you should be able to accomplish this. This type of scenario is pretty common and there is a built-in "Event" card in Okta - User Okta Profile Updated which will create an event hook for the event (user.account.update_profile) with the Event Hook payload destination being that Workflow.
So each time a users profile is updated in your environment a payload will be delivered. There is a changedAttributes field than can then be evaluated for a change to a specific attribute and if "false" stop processing. Example: (attributetoEvaluate is a placeholder. I am assuming you mean the default attribute "mobilePhone" based on your question. If so, it would be used instead of the placeholder)
So assuming one of the changedAttributes were "attributeToEvaluate" the flow would continue processing. You could then obtain the User's ID from the User Okta Profile Updated and use it to "read" the user's current attribute value. Then construct your new login. And finally, update the user login with this new value.
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
@yc954 (yc954) - So assuming the user is "Okta Sourced" && you mean they "update their Okta profile" with a new attribute and you then need to change their login to an alternate value you should be able to accomplish this. This type of scenario is pretty common and there is a built-in "Event" card in Okta - User Okta Profile Updated which will create an event hook for the event (user.account.update_profile) with the Event Hook payload destination being that Workflow.
So each time a users profile is updated in your environment a payload will be delivered. There is a changedAttributes field than can then be evaluated for a change to a specific attribute and if "false" stop processing. Example: (attributetoEvaluate is a placeholder. I am assuming you mean the default attribute "mobilePhone" based on your question. If so, it would be used instead of the placeholder)
So assuming one of the changedAttributes were "attributeToEvaluate" the flow would continue processing. You could then obtain the User's ID from the User Okta Profile Updated and use it to "read" the user's current attribute value. Then construct your new login. And finally, update the user login with this new value.