The Experts below are selected from a list of 9615 Experts worldwide ranked by ideXlab platform
Simon Josefsson - One of the best experts on this subject based on the ideXlab platform.
-
A Simple Authentication and Security Layer (SASL) and Generic Security Service Application Program Interface (GSS-API) Mechanism for OpenID
2012Co-Authors: Eliot Lear, Hannes Tschofenig, Henry Mauldin, Simon JosefssonAbstract:OpenID has found its usage on the Internet for Web Single Sign-On. Simple Authentication and Security Layer (SASL) and the Generic Security Service Application Program Interface (GSS-API) are application frameworks to generalize Authentication. This memo specifies a SASL and GSS-API mechanism for OpenID that allows the integration of existing OpenID Identity Providers with applications using SASL and GSS-API. [STANDARDS-TRACK]
-
using generic security service application program interface gss api mechanisms in Simple Authentication and security layer sasl the gs2 mechanism family
RFC, 2010Co-Authors: N. Williams, Simon JosefssonAbstract:This document describes how to use a Generic Security Service Application Program Interface (GSS-API) mechanism in the the Simple Authentication and Security Layer (SASL) framework. This is done by defining a new SASL mechanism family, called GS2. This mechanism family offers a number of improvements over the previous "SASL/ GSSAPI" mechanism: it is more general, uses fewer messages for the Authentication phase in some cases, and supports negotiable use of channel binding. Only GSS-API mechanisms that support channel binding are supported. See for more information.
Alexey Melnikov - One of the best experts on this subject based on the ideXlab platform.
-
salted challenge response Authentication mechanism scram sasl and gss api mechanisms
RFC, 2010Co-Authors: Abhijit Menonsen, Alexey Melnikov, N. Williams, C. NewmanAbstract:The secure Authentication mechanism most widely deployed and used by Internet application protocols is the transmission of clear-text passwords over a channel protected by Transport Layer Security (TLS). There are some significant security concerns with that mechanism, which could be addressed by the use of a challenge response Authentication mechanism protected by TLS. Unfortunately, the challenge response mechanisms presently on the standards track all fail to meet requirements necessary for widespread deployment, and have had success only in limited use. This specification describes a family of Simple Authentication and Security Layer (SASL; RFC 4422) Authentication mechanisms called the Salted Challenge Response Authentication Mechanism (SCRAM), which addresses the security concerns and meets the deployability requirements. When used in combination with TLS or an equivalent security layer, a mechanism from this family could improve the status quo for application protocol Authentication and provide a suitable choice for a mandatory-to- implement mechanism for future application protocol standards. [STANDARDS-TRACK]
-
lightweight directory access protocol ldap schema for storing salted challenge response Authentication mechanism scram secrets
RFC, 2010Co-Authors: Alexey MelnikovAbstract:This memo describes LDAP schema for storing secrets used by Salted Challenge Response (SCRAM) Simple Authentication and Security Layer (SASL) Mechanism. Note A revised version of this draft document will be submitted to the RFC editor as a Proposed Standard for the Internet Community. Discussion and suggestions for improvement are requested, and should be sent to ietf-sasl@imc.org.
N. Williams - One of the best experts on this subject based on the ideXlab platform.
-
salted challenge response Authentication mechanism scram sasl and gss api mechanisms
RFC, 2010Co-Authors: Abhijit Menonsen, Alexey Melnikov, N. Williams, C. NewmanAbstract:The secure Authentication mechanism most widely deployed and used by Internet application protocols is the transmission of clear-text passwords over a channel protected by Transport Layer Security (TLS). There are some significant security concerns with that mechanism, which could be addressed by the use of a challenge response Authentication mechanism protected by TLS. Unfortunately, the challenge response mechanisms presently on the standards track all fail to meet requirements necessary for widespread deployment, and have had success only in limited use. This specification describes a family of Simple Authentication and Security Layer (SASL; RFC 4422) Authentication mechanisms called the Salted Challenge Response Authentication Mechanism (SCRAM), which addresses the security concerns and meets the deployability requirements. When used in combination with TLS or an equivalent security layer, a mechanism from this family could improve the status quo for application protocol Authentication and provide a suitable choice for a mandatory-to- implement mechanism for future application protocol standards. [STANDARDS-TRACK]
-
using generic security service application program interface gss api mechanisms in Simple Authentication and security layer sasl the gs2 mechanism family
RFC, 2010Co-Authors: N. Williams, Simon JosefssonAbstract:This document describes how to use a Generic Security Service Application Program Interface (GSS-API) mechanism in the the Simple Authentication and Security Layer (SASL) framework. This is done by defining a new SASL mechanism family, called GS2. This mechanism family offers a number of improvements over the previous "SASL/ GSSAPI" mechanism: it is more general, uses fewer messages for the Authentication phase in some cases, and supports negotiable use of channel binding. Only GSS-API mechanisms that support channel binding are supported. See for more information.
Abhijit Menonsen - One of the best experts on this subject based on the ideXlab platform.
-
salted challenge response Authentication mechanism scram sasl and gss api mechanisms
RFC, 2010Co-Authors: Abhijit Menonsen, Alexey Melnikov, N. Williams, C. NewmanAbstract:The secure Authentication mechanism most widely deployed and used by Internet application protocols is the transmission of clear-text passwords over a channel protected by Transport Layer Security (TLS). There are some significant security concerns with that mechanism, which could be addressed by the use of a challenge response Authentication mechanism protected by TLS. Unfortunately, the challenge response mechanisms presently on the standards track all fail to meet requirements necessary for widespread deployment, and have had success only in limited use. This specification describes a family of Simple Authentication and Security Layer (SASL; RFC 4422) Authentication mechanisms called the Salted Challenge Response Authentication Mechanism (SCRAM), which addresses the security concerns and meets the deployability requirements. When used in combination with TLS or an equivalent security layer, a mechanism from this family could improve the status quo for application protocol Authentication and provide a suitable choice for a mandatory-to- implement mechanism for future application protocol standards. [STANDARDS-TRACK]
-
the post office protocol pop3 Simple Authentication and security layer sasl Authentication mechanism
RFC, 2007Co-Authors: Abhijit Menonsen, Robert SiemborskiAbstract:This document defines a profile of the Simple Authentication and Security Layer (SASL) for the Post Office Protocol (POP3). This extension allows a POP3 client to indicate an Authentication mechanism to the server, perform an Authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions during this session. This document seeks to consolidate the information related to POP3 AUTH into a single document. To this end, this document obsoletes and replaces RFC 1734, and updates the information contained in Section 6.3 of RFC 2449. [STANDARDS-TRACK]
C. Newman - One of the best experts on this subject based on the ideXlab platform.
-
salted challenge response Authentication mechanism scram sasl and gss api mechanisms
RFC, 2010Co-Authors: Abhijit Menonsen, Alexey Melnikov, N. Williams, C. NewmanAbstract:The secure Authentication mechanism most widely deployed and used by Internet application protocols is the transmission of clear-text passwords over a channel protected by Transport Layer Security (TLS). There are some significant security concerns with that mechanism, which could be addressed by the use of a challenge response Authentication mechanism protected by TLS. Unfortunately, the challenge response mechanisms presently on the standards track all fail to meet requirements necessary for widespread deployment, and have had success only in limited use. This specification describes a family of Simple Authentication and Security Layer (SASL; RFC 4422) Authentication mechanisms called the Salted Challenge Response Authentication Mechanism (SCRAM), which addresses the security concerns and meets the deployability requirements. When used in combination with TLS or an equivalent security layer, a mechanism from this family could improve the status quo for application protocol Authentication and provide a suitable choice for a mandatory-to- implement mechanism for future application protocol standards. [STANDARDS-TRACK]