This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Authentication Method Reference Values
Authentication Method Reference Values

Version management

Difference between version and

At line 1 added 45 lines
!!! Overview[1]
[{$pagename}] ([amr_values]) is defined in [RFC 8176] and creates a Authentication Method Reference Values Registry [IANA Registry] [Authentication Method Reference Values|https://www.iana.org/assignments/authentication-method-reference-values/authentication-method-reference-values.xhtml#amr-values|target='_blank'].
The "[amr]" ([Authentication Method Reference]) [claim] is defined and registered in the [IANA] "[JSON Web Token Claims]" registry [IANA.JWT.Claims], but no standard [{$pagename}] are currently defined. [RFC 8176] specification establishes a registry for Authentication Method Reference values and defines an initial set of [{$pagename}].
The following is a list of [{$pagename}] defined by the [Authentication Method Reference Values] specification:
%%zebra-table
%%sortable
%%table-filter
||Value||Description
|[face|Facial recognition]|[Facial recognition]
|[fpt]|[Fingerprint recognition] [Biometric Authentication]
|[geo]|[Geolocation]
|[hwk]|[Proof-of-Possession] ([PoP]) of a [hardware-secured key]. See Appendix C of [RFC 4211] for a discussion on [PoP].
|[iris|Iris recognition]|[Iris recognition]
|[kba|KBA]|[Knowledge-based authentication|Knowledge Factor] [NIST.SP.800-63]
|[mca|MCA]|[Multiple-channel Authentication]. The authentication involves communication over more than one distinct channel.
|[mfa|MFA]|[Multi-Factor Authentication] [NIST.SP.800-63]. When this is present, specific [Authentication Methods] used may also be included.
|[otp|OTP]|[One-Time password]. [One-Time password] specifications that this [Authentication Method] applies to include [RFC 4226] and [RFC 6238].
|[pin|PIN]|[Personal Identification Number] or pattern (not restricted to containing only numbers) that a user enters to unlock a key on the device. This mechanism SHOULD have a way to deter an attacker from obtaining the PIN by trying repeated guesses.
|[pwd]|[Password-based] [Authentication]
|[rba|Risk-Based Authentication]|[Risk-Based Authentication] [JECM]
|[retina|Retinal recognition]|[Retinal scan|Retinal recognition] [Biometric Authentication]
|[sc|Smart Card]|[Smart Card]
|[sms|SMS]|Confirmation using [SMS] message to the user at a registered number
|[swk]|[Proof-of-Possession] ([PoP]) of a [Software-secured key]. See Appendix C of [RFC 4211] for a discussion on [PoP].
|[tel]|Confirmation by telephone call to the user at a registered number
|user|User [presence] test
|[vbm]|[Voice recognition] by [Biometric Authentication]
|[wia|WIA]|[Windows Integrated Authentication], as described in [MSDN]
/%
/%
/%
!! Where Used
[{$pagename}] __SHOULD__ be used for all of the following:
* [amr]
* [amr_values]
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Authentication Method Reference Values draft-jones-oauth-amr-values-03|https://tools.ietf.org/html/draft-jones-oauth-amr-values-03#section-7.1|target='_blank'] - based on information obtained 2013-04-10
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop