You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
With some debugging, that method doesn’t correctly create a user fully. It was missing some fields like the “recovery_question” and answer.
I did some digging around in the source code of express-stormpath and found this:
"Our application creates users programmatically and I was creating users like so:
const spApplication = req.app.get('stormpathApplication');
spApplication.createAccount(acct);
With some debugging, that method doesn’t correctly create a user fully. It was missing some fields like the “recovery_question” and answer.
I did some digging around in the source code of
express-stormpath
and found this:express-stormpath/lib/controllers/register.js
Line 175 in aed8d26
oktaUser.profile.emailVerificationStatus = 'UNVERIFIED';
oktaUser.profile.emailVerificationToken = uuid.v4();
oktaUser.profile.stormpathMigrationRecoveryAnswer = uuid.v4();
oktaUser.credentials.recovery_question = {
question: 'stormpathMigrationRecoveryAnswer',
answer: oktaUser.profile.stormpathMigrationRecoveryAnswer
};
So I finally had to create a user manually using the okta node sdk.
Without these fields, the reset password would fail silently."
The text was updated successfully, but these errors were encountered: