Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix typo in readme #612

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix typo in readme #612

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion policies/totp/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ The claim *totpIdentifier* is used to copy the different type of signIn options

## Just In Time TOTP Migration

Jut In time migration allows you to migrate from your legacy storage of the TOTP Secret to the new TOTP method outlined above.
Just In time migration allows you to migrate from your legacy storage of the TOTP Secret to the new TOTP method outlined above.
If you were previously using the [TOTP multi-factor authentication](../custom-mfa-totp) policy sample to implement TOTP then your users Secrets will be stored in the 'extension_StrongAuthenticationAppSecretKey' extension attribute.

To migrate these to the new method you can implement the [TOTP Migration Extension](policy/TrustFrameworkExtensions_TOTPMigration.xml) policy as the parent policy for either [SignUpOrSignIn_TOTP](policy/SignUpOrSignin_TOTP.xml#L9) or [PasswordReset_TOTP.xml](policy/PaswordReset_TOTP.xml#L9)
Expand Down