Search results

'''Category''': Cryptographic Protocol Specification [[Category:Cryptographic Protocol Specification]]

'''Category''': Credential Requirements Specification Specification for PIV; SP 800-78, Cryptographic Algorithms and Key Sizes for PIV; SP 800-79, Guidelines

Data values, other than keys, that are required to operate cryptographic modules and that need to be protected e.g., a PIN, a pass-phrase, or a key Private data, other than keys, that are required to access cryptographic modules.

...some further steps. Typically, this involves the use of a registered SAML protocol binding. This technique is used in the browser/artifact profile of SAML. ...structured data object pointing to a typically larger, variably-sized SAML protocol message. SAML artifacts are designed to be embedded in URLs and conveyed in

Authentication protocol specification ...access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosur

...ficates and internal directory systems because of its adoption by the IETF protocol [https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol LDAP]. ...ingle sign-on across MIT in 1983. [https://en.wikipedia.org/wiki/Kerberos_(protocol) Kerberos] later surfaced in many commercial identity systems like FreeBSD,

'''Category''': Trust Framework Provider Specification ...l Management]], [[Credential Service]], [[Credential Service Provider]], [[Cryptographic Token]], [[Electronic Credentials]], [[Electronic Trust Service]], [[Electr

...-announce/afYBtwSr79TXcAhCoO4IXo1ePUg/ Grant Negotiation and Authorization Protocol (GNAP) is a new effort in the IETF] to create a new version to replace [[OA ...particular values to be used in the amr Claim is beyond the scope of this specification. Parties using this claim will need to agree upon the meanings of the value