AM implements the following RFCs, Internet-Drafts, and standards:
RFC 4226: HOTP: An HMAC-Based One-Time Password Algorithm, supported by the OAUTH authentication module.
RFC 6238: TOTP: Time-Based One-Time Password Algorithm, supported by the OAUTH authentication module.
In section 5.6 of this specification, AM supports Normal Claims. The optional Aggregated Claims and Distributed Claims representations are not supported by AM.
AM applies the guidelines suggested by the OpenID Financial-grade API (FAPI) Working Group to the implementation of CIBA, which shapes the support of CIBA in AM:
AM only supports the CIBA "poll" mode, not the "push" or "ping" modes.
AM requires use of confidential clients for CIBA.
AM requires use of signed JSON-web tokens (JWT) to pass parameters, using one of the following algorithms:
ES256- ECDSA with SHA-256 and NIST standard P-256 elliptic curve.
PS256- RSASSA-PSS using SHA-256.
Plain JSON or form parameters for CIBA-related data is not supported.
AM supports SAML v2.0; support for SAML v1.1 and v1.0 was removed in AM 7, although WS-Federation functionality still creates assertions in SAML v1.x format.
SAML Specifications are available from the OASIS standards page.
Query string signatures:
Recommendation E.146, concerning Mobile Subscriber ISDN Numbers (MSISDN), supported for authentication.
RFC 1271: Remote Network Monitoring Management Information Base, supported for monitoring over SNMP.
RFC 2578: Structure of Management Information Version 2 (SMIv2), supported for monitoring over SNMP.
RFC 2579: Textual Conventions for SMIv2, supported for monitoring over SNMP.
RFC 2617: HTTP Authentication: Basic and Digest Access Authentication, supported as an authentication module.
RFC 2865: Remote Authentication Dial In User Service (RADIUS), supported as an AM service.
RFC 4510: Lightweight Directory Access Protocol (LDAP), for authentication modules and when accessing data stores.
RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, supported for certificate-based authentication.
RFC 6265: HTTP State Management Mechanism regarding HTTP Cookies and
Set-Cookie header fields.