ghrc2 (ghrc2) asked a question.
Self-service registration with separate Username and Email?
I'm trying to enable self-service registration, but I want users to be able to choose a login/username which is separate from their primary email.
In profile editor, I'm able to relax the format restriction for 'login', but it appears that the self-service registration customization doesn't allow adding separate input fields for both 'email' and 'login'. According to the docs:
- Note: Upon registering, end users need to provide an email address. Okta automatically uses that email address as the end user’s username and primary email address.
...which is not what I want.
Is there any way in Okta to easily do this? If not, that seems like a huge limitation.
I have created users with different username and email.
The way that it works from UI is first enter the email address and then the username.
See below comment. I am not trying to use Okta for SSO, but for customer identity.
I dont think so you are able to add user name field on Self Service Registration form as you mentioned per document, thats kind of restriction. The easiest way if once the user get registered, administrator can rename the user name (not a good approach as OKTA wants treat user name in email format).
Before going to do anything, why you wish to do it ? if any application has a requirement then you can manage that by doing username override easily.
https://help.okta.com/en/prod/Content/Topics/Directory/ad-agent-override-username-format.htm
I was hoping to use Okta Customer Identity (not Workforce Identity/SSO) for authentication/identity services for a mobile app. Plenty of websites and apps today have separate logins and email addresses, and it's of course not reasonable to require manual administrative action after sign-up.
Per https://www.okta.com/blog/2017/07/decoding-customer-iam-ciam-vs-iam/
"If the CIAM provider doesn’t make it simple for a developer to register, login, and manage user accounts for their applications, they need to find a new provider."
Sounds like unless I want to switch to my own registration UI instead of using Okta's browser-based registration (which I'd rather not do for a small mobile app), Okta hints I may need to find a new provider. Still hoping there's a way to do this since Okta looks like a great product offering otherwise.
i agree with you and there is a idea raised to OKTA -
https://ideas.okta.com/app/#/case/113685
Thanks. While that looks like it was for an enterprise/workforce use case, the feature request is exactly the same and I added my +1 to it.
I just checked out a competitor of Okta's and was able to do this right away; it's disappointing Okta doesn't support this and isn't on the roadmap.