-
Notifications
You must be signed in to change notification settings - Fork 84
Support amr
claim.
#136
Comments
If I understand the suggestions correctly: amr values
|
When using two-factor authentication with a Microsoft account and the Microsoft authenticator app, Microsoft's servers will push a notification to the app on a sign-in attempt. The app then has two options: authorize the request or deny it. In this case, this isn't |
So, in digging some more, it might be smart to do both acr and amr at the same time. In many cases they are related within the process. For our use case we only have one authenticating authority so we don't care about acr, but I see the use case for others.
acr is a single value (and defined) and amr is a multi-valued whatever the as and client agree upon. |
@vsimonian those values are still up in the air right now, it's a draft spec. I'm sure they will change over time. I'm assuming in the MSFT case they would treat that as an otp. |
Working on this in a new branch. We now have basic support for the When a user authenticates with the local password provider, the Please comment with requirements for other authentication methods, configurability, etc. |
#141 has been merged. Documentation is necessary. |
Documented - merged connect-docs/#25 |
Leaving open for review. cc @topperge |
When ID Tokens are issued they should optionally include the
amr
claim. This claim represents the authentication methods used to sign in the user. There's an IETF draft Authentication Method Reference Values that defines an initial set of values.The values for the claim could be defined in provider configuration. We could keep track on req.session of which methods are active for a given session. These should potentially have different TTLs, etc.
The text was updated successfully, but these errors were encountered: