
User16183943605507582026 (Customer) asked a question.
Currently, we don't have our end user's primary email address and contact number. They have their unique application username and password for our application. We are busy implementing Okta into our app.
The current user base will be imported into Okta (pre-registered) and will use their existing unique application username and password to sign into Okta.
However, in future We'd like ours users to use their primary email address as the username.
Is there a configuration setting to say upon first Okta Sign In direct the user to capture their primary email and/or contact number?
What is the best approach?

The username is the same as the primary email, if you want a different primary email, Okta needs to take it's value from somewhere, for example a mapping from AD to Okta, or having an CSV file updated in Okta where that primary email is specified.
You can also setup Self Service Registration and users create their own accounts in Okta and you can specify there what fields should be required from Directory - SSR.
To get more in depth I would recommend opening up a support ticket with Okta to further discuss over a meeting.
Thank you.
Please see my response in italics below
The username is the same as the primary email, if you want a different primary email, Okta needs to take its value from somewhere, for example, a mapping from AD to Okta, or having a CSV file updated in Okta where that primary email is specified.
You can also setup Self Service Registration and users create their own accounts in Okta and you can specify there what fields should be required from Directory - SSR.
Connect to ad or o365 n pull the info and use ad as identity source.
u can use a read only account if u dont want okta to touch your ad