Migrate User Passwords with Okta’s Password Hook
Learn how to use Okta’s inline password hook to make user migration easier.
Migrate User Passwords with Okta’s Password Hook
Learn how to use Okta’s inline password hook to make user migration easier.
Pritam Jadhav
Hi Heather,
Thanks for this great article on Password import inline hook. We could successfully integrate the hook but need more data in incoming request from Okta like the ClientId. Is there any way to do this. I could see we can add custom header name/value collection in inline hook, so is wondering if we can use the okta expression to add the client id may be like request.clientid
or in any other way.
Please let me know if there is another way to achieve this. Thanks in advance.
Hi Heather,
Thanks for putting this up, is the database still up and working, for me it is giving credential error for correct password.
Alex
Hi @Alexapp!
I’m not very familiar with how Glitch works, but the DB that is created should be part of the glitch project:
It’s all initialized when the project runs.
I am working on a newer version of this post that uses a Java (Spring Boot) backend to handle the hook. Let us know if you have any general questions about how this hook works!
(If you have a specific language/framework you are using, that would be helpful too!)
This is working now, the option was set as ‘var hashed = true;’ for hash password to work, hence the plaintext was not working initially. I have updated in the code, and it works as expected.
Nice work, and demo, will help many clients.
Awesome! Thanks for following up!
Hi, thanks for the nice article. I’m interested if the password hooks available in all subscription plans?