<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5WR00002L8G450AFOkta Classic EngineAuthenticationAnswered2026-11-05T06:49:16.000Z2026-10-27T01:54:02.000Z2026-11-05T06:49:16.000Z

kanakos.23654 (Customer) asked a question.

Question Regarding Updating the Default Okta User Profile Policy

Dear Okta Team,

We have added a user profile policy under Okta Admin Console > Security > User Profile Policies to allow users to sign in using their email addresses, in addition to their existing username format of LastName.FirstName.

Going forward, we would like users to be able to sign in with their email addresses to Okta and all applications integrated with Okta.

Would it be safe to update the default policy as well to allow sign-in using email addresses? If changing the default policy could cause any issues or have any potential impact, we would appreciate your advice.

Thank you in advance for your guidance.


Mihai N. likes this.
  • Mihai N. (Okta, Inc.)

    Hi @kanakos.23654 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    Yes, you can update the default User Profile Policy to allow sign-in with an email address, but you should review a few potential risks and configuration impacts before making the change.

    Because the default User Profile Policy acts as a "catch-all" and applies to the Okta Dashboard, administrative access, and any applications that do not have a specific policy assigned, updating it has org-wide implications.

     

    Keep and eye out for the following: 

     

    1. Uniqueness Conflicts (Shared Email Addresses)

    When you allow an attribute (like email) to be used as a sign-in identifier, Okta relies on that value being strictly unique across the entire directory.

    • The Risk: If you have contractors, administrative accounts (e.g., an admin account and a standard user account belonging to the same person), service accounts, or test accounts that share a single email address, Okta will not be able to resolve which account is attempting to log in. This can result in authentication failures or account lockouts for those specific users.

     

    2. Attribute Permissions (Read-Write Exposure)

    Depending on how you configure the enrollment form within the User Profile Policy, custom identifiers sometimes require the attribute's permission to be set to Read-Write in the Okta Profile Editor.

    • The Risk: While Active Directory-mastered users will still be blocked from editing their email (as AD remains the source of truth), Okta-mastered users (such as external partners or local service accounts) could potentially log into their Okta dashboard and change their own email addresses. Ensure your Profile Editor permissions remain locked down if you do not want users self-modifying their email.

     

    3. Increased Attack Surface

    Using a proprietary LastName.FirstName format provides a mild layer of obscurity, as attackers must guess or know your internal naming convention.

    • The Risk: Email addresses are widely available in public data breaches. Applying this to the default policy means your Okta Admin Console and all default apps are now susceptible to credential stuffing and brute-force attacks targeting user email addresses. Ensure your Global Session Policies and ThreatInsight configurations are hardened to drop suspicious traffic before making this change.

     

    4. Downstream App Assertions Remain Unchanged

    Changing the User Profile Policy only changes how the user authenticates into the Okta Sign-In Widget. It does not alter the underlying username format sent to downstream applications via SAML or OIDC.

    • If an application is configured to expect the LastName.FirstName Okta username in the SAML NameID subject, Okta will continue to send LastName.FirstName, even if the user typed their email address at the Okta login screen.

     

    Recommendation

    Before updating the default policy:

    1. Run a uniqueness check: Export a report of your Okta users and check for duplicate email addresses. Resolve any duplicates (especially on admin and service accounts) before proceeding.
    2. Test via a custom policy first: You can safely apply the email identifier to a new custom User Profile Policy and assign it to a broad group of test applications (and users) to monitor for help desk tickets before finally committing the change to the permanent default policy.

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • Mihai N. (Okta, Inc.)

    Hi @kanakos.23654 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    Yes, you can update the default User Profile Policy to allow sign-in with an email address, but you should review a few potential risks and configuration impacts before making the change.

    Because the default User Profile Policy acts as a "catch-all" and applies to the Okta Dashboard, administrative access, and any applications that do not have a specific policy assigned, updating it has org-wide implications.

     

    Keep and eye out for the following: 

     

    1. Uniqueness Conflicts (Shared Email Addresses)

    When you allow an attribute (like email) to be used as a sign-in identifier, Okta relies on that value being strictly unique across the entire directory.

    • The Risk: If you have contractors, administrative accounts (e.g., an admin account and a standard user account belonging to the same person), service accounts, or test accounts that share a single email address, Okta will not be able to resolve which account is attempting to log in. This can result in authentication failures or account lockouts for those specific users.

     

    2. Attribute Permissions (Read-Write Exposure)

    Depending on how you configure the enrollment form within the User Profile Policy, custom identifiers sometimes require the attribute's permission to be set to Read-Write in the Okta Profile Editor.

    • The Risk: While Active Directory-mastered users will still be blocked from editing their email (as AD remains the source of truth), Okta-mastered users (such as external partners or local service accounts) could potentially log into their Okta dashboard and change their own email addresses. Ensure your Profile Editor permissions remain locked down if you do not want users self-modifying their email.

     

    3. Increased Attack Surface

    Using a proprietary LastName.FirstName format provides a mild layer of obscurity, as attackers must guess or know your internal naming convention.

    • The Risk: Email addresses are widely available in public data breaches. Applying this to the default policy means your Okta Admin Console and all default apps are now susceptible to credential stuffing and brute-force attacks targeting user email addresses. Ensure your Global Session Policies and ThreatInsight configurations are hardened to drop suspicious traffic before making this change.

     

    4. Downstream App Assertions Remain Unchanged

    Changing the User Profile Policy only changes how the user authenticates into the Okta Sign-In Widget. It does not alter the underlying username format sent to downstream applications via SAML or OIDC.

    • If an application is configured to expect the LastName.FirstName Okta username in the SAML NameID subject, Okta will continue to send LastName.FirstName, even if the user typed their email address at the Okta login screen.

     

    Recommendation

    Before updating the default policy:

    1. Run a uniqueness check: Export a report of your Okta users and check for duplicate email addresses. Resolve any duplicates (especially on admin and service accounts) before proceeding.
    2. Test via a custom policy first: You can safely apply the email identifier to a new custom User Profile Policy and assign it to a broad group of test applications (and users) to monitor for help desk tickets before finally committing the change to the permanent default policy.

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • kanakos.23654 (Customer)

    Sorry for the delayed response. Thank you very much for your comments. extremely helpful!

Loading
Question Regarding Updating the Default Okta User Profile Policy
Okta Support Agent (Beta)

Terms of Service

Hello! I'm the Okta Support Agent (Beta), your go-to resource for questions about Okta products. Please remember for your security and privacy, do not share any Personally Identifiable Information (PII) such as passwords, IP addresses, or other details with me.

Okta Privacy Policy and Terms of Service apply