<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
0D51Y00006EnYf4SAFOkta Classic EngineAdministrationAnswered2024-04-23T16:15:28.000Z2019-05-08T23:51:16.000Z2019-05-10T22:23:39.000Z

NickL.43635 (Customer) asked a question.

Importing a User with a SHA-1 Hashed Password

I am trying to do a test user import for my company as we are switching from managing users in our database to using Okta as our identity provider. We'd like to keep the transition for our users as easy as possible, so we want to port over all of our current users with their current passwords. I have been able to successfully create a new user in Okta through the user API with using the password salt and hashed password. However, when I go to log in with the newly created user, the password does not seem to work.

 

In the Okta admin screen the user is in Okta and activated. I am unsure as to why the password is not working. I have been using this as a resource: https://developer.okta.com/docs/api/resources/users/*create-user-with-imported-hashed-password

 

Everything seems to be working correctly except for new user being unable to log in. Any guidance would be appreciated.


  • SivaDesetti (Waste Management)

    Hi Nick,

    This is expected behavior.. If there is an issue with salt order or encoded format.

    I think .. OKTA supports only SHA2 passwords, support to SHA1 is early feature or something needs to be turned on..check with support.

     

    Okta is strict with Salt order, please check above points..

     

    Thanks

    Siva Desetti

     

    Expand Post
    Selected as Best
  • Vlad here with Okta's Customer Support Team, thank you for reaching out to us.

    Unfortunately, our department cannot reproduce this issue. I recommend opening a new ticket with our support team or sending an email directly to our developer team at developer@okta.com

  • SivaDesetti (Waste Management)

    Hi Nick,

    This is expected behavior.. If there is an issue with salt order or encoded format.

    I think .. OKTA supports only SHA2 passwords, support to SHA1 is early feature or something needs to be turned on..check with support.

     

    Okta is strict with Salt order, please check above points..

     

    Thanks

    Siva Desetti

     

    Expand Post
    Selected as Best
This question is closed.
Loading
Importing a User with a SHA-1 Hashed Password