<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
0D51Y00006CJxwLSATOkta Classic EngineAdministrationAnswered2024-03-25T14:56:35.000Z2019-04-30T10:35:45.000Z2021-02-16T16:17:56.000Z

DennisP.64707 (Customer) asked a question.

force login to always use full email addresses

I'm sure I'm just missing a setting here but if anyone knows please can you call it out.

if I have a user with a login as "fred@fred.com" this user can login with either "fred" or "fred@fred.com" as long as no other users exist with a login of "fred@anything.any".

 

I'm looking to stop this feature an ensure all users must use their full email address all the time.


EricD.38212 likes this.
  • ​Hi Dennis,

     

    Currently, we do not have a functionality that would allow editing domain restrictions on the email field in the sign-in page.  

    Selected as Best
  • ​Hi Dennis,

     

    Currently, we do not have a functionality that would allow editing domain restrictions on the email field in the sign-in page.  

    Selected as Best
  • ma96g (ma96g)

    I'm also having the same issue. It's ridiculous that this feature doesn't exist. The only reason anyone uses Okta is for security, and you're saying I can't make users enter their entire email to log in? This is a major oversight on Okta's part , and I would strongly suggest you add it. I'm shocked that this is something you're aware of and still haven't done anything to remedy.

  • FrankS.32049 (Bandwidth)

    And here we are Feb 2021 and still the same issue. Nothing has changed. In our setup we even removed the restriction of usernames having to be email formatted.

     

    To go with the example, if a new user "fred@othercompany.com" where to be added this would break the login flow for "fred@fred.com" because now there are two "fred" users. Or, in my case, a user "fred" could get added, now whenever "fred@fred.com" (remember the happy user logging in without entering their domain) is not actually trying to login as "fred", which of course won't work, but it'll look like someone is trying to get access to "fred", even though it's just he unwitting "fred@fred.com" wondering what in the world happened. One day it works, the next it doesn't.

     

    Okta, what are you doing?

    Expand Post
  • FrankS.32049 (Bandwidth)

    Re my earlier comment about having two users and the second breaking the first user's experience.

     

    According to Okta support:

     

    You will not have any type of issues with this type of configuration.

    We will not match users between them.

    For example: if you have test1@domain1.com and you create test1@domain2.com, the first one will be able to connect with prefix only or with the suffix as well, the second one will be able to connect ONLY via domain2.com suffix, so he cannot access the first account based on the same name.

     

     

    Still sounds like a bug, and not a feature, to me. I still want to be able to disable this. Grumble.

    Expand Post
This question is closed.
Loading
force login to always use full email addresses