The Experts below are selected from a list of 345780 Experts worldwide ranked by ideXlab platform
Nicolas Williams - One of the best experts on this subject based on the ideXlab platform.
-
using generic security service Application Program interface gss api mechanisms in simple authentication and security layer sasl the gs2 mechanism family
RFC, 2010Co-Authors: Nicolas 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.
-
Using Generic Security Service Application Program Interface (GSS-API
2010Co-Authors: Nicolas WilliamsAbstract:This document defines a new function for the Generic Security Service Application Program Interface (GSS-API), which allows Applications to store delegated (and other) credentials in the implicit GSS-API credential store. This is needed for GSS-API Applications to use delegated credentials as they would use other credentials. Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as th
-
Using Generic Security Service Application Program Interface (GSS-API
2010Co-Authors: Nicolas WilliamsAbstract:This document defines a new function for the Generic Security Service Application Program Interface (GSS-API), which allows Applications to store delegated (and other) credentials in the implicit GSS-API credential store. This is needed for GSS-API Applications to use delegated credentials as they would use other credentials. Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards " (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents in effect on the date of publication of this documen
-
a pseudo random function prf api extension for the generic security service Application Program interface gss api
RFC, 2006Co-Authors: Nicolas WilliamsAbstract:This document defines a Pseudo-Random Function (PRF) extension to the Generic Security Service Application Program Interface (GSS-API) for keying Application protocols given an established GSS-API security context. The primary intended use of this function is to key secure session layers that do not or cannot use GSS-API per-message message integrity check (MIC) and wrap tokens for session protection. [STANDARDS-TRACK]
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: Nicolas 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.
J. Linn - One of the best experts on this subject based on the ideXlab platform.
-
generic security service Application Program interface version 2 update 1
RFC, 2000Co-Authors: J. LinnAbstract:The Generic Security Service Application Program Interface (GSS-API), Version 2, as defined in [RFC-2078], provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of Applications to different environments. This specification defines GSS-API services and primitives at a level independent of underlying mechanism and Programming language environment, and is to be complemented by other, related specifications:
-
Generic Security Service Application Program Interface, Version 2
1997Co-Authors: J. LinnAbstract:The Generic Security Service Application Program Interface (GSS-API), as defined in RFC-1508, provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of Applications to different environments. This specification defines GSS-API services and primitives at a level independent of underlying mechanism and Programming language environment, and is to be complemented by other, related specifications:
-
Generic Security Service Application Program Interface
1993Co-Authors: J. LinnAbstract:This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of Applications to different environments. This specification defines GSS-API services and primitives at a level independent of underlying mechanism and Programming language environment, and is to be complemented by other, related specifications:
Sam Hartman - One of the best experts on this subject based on the ideXlab platform.
-
desired enhancements to generic security services Application Program interface gss api version 3 naming
RFC, 2006Co-Authors: Sam HartmanAbstract:The Generic Security Services API (GSS-API) provides a naming architecture that supports name-based authorization. GSS-API authenticates two named parties to each other. Names can be stored on access control lists to make authorization decisions. Advances in security mechanisms and the way implementers wish to use GSS-API require this model to be extended for the next version of GSS-API. As people move within an organization or change their names, the name authenticated by GSS-API may change. Using some sort of constant identifier would make ACLs more stable. Some mechanisms such as public-key mechanisms do not have a single name to be used across all environments. Other mechanisms such as Kerberos may include group membership or role information as part of authentication. This document motivates extensions to GSS-API naming and describes the extensions under discussion.
-
the kerberos version 5 generic security service Application Program interface gss api mechanism version 2
RFC, 2005Co-Authors: Larry Zhu, Sam Hartman, Karthik JaganathanAbstract:This document defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (GSS-API) when using the Kerberos Version 5 mechanism. RFC 1964 is updated and incremental changes are proposed in response to recent developments such as the introduction of Kerberos cryptosystem framework. These changes support the inclusion of new cryptosystems, by defining new per-message tokens along with their encryption and checksum algorithms based on the cryptosystem profiles. [STANDARDS-TRACK]
Yoon Jong Min - One of the best experts on this subject based on the ideXlab platform.
-
method for wirelessly processing certification using ip address of wireless terminal equipped with ic card or Application Program
2004Co-Authors: Hong Jong Cheol, Kim Jae Hyung, Yoon Jong MinAbstract:PURPOSE: A method for wirelessly processing certification using an IP(Internet Protocol) address of a wireless terminal equipped with an IC card or an Application Program is provided to reliably/conveniently process a contract needing the certification/digital signature through wireless Internet connection by storing a certificate that a user is responsible for the certification in the wireless terminal. CONSTITUTION: An IP address agency assigns/offers the IP address to the wireless terminal. The wireless terminal stores the IP address to a memory(720). After connecting to a web server of a client, the wireless terminal transmits the stored IP address to the web server when the web server requests the certification for the client(730). The web server requests the certification to the IP address agency by transmitting the IP address to the IP address agency(735). The IP address agency processes the certification for the client by referring to the IP address received from the web server and transmits certification processing result data to the web server(740).
-
method for wirelessly processing certification using ip address of wireless terminal equipped with ic card or Application Program
2004Co-Authors: Hong Jong Cheol, Kim Jae Hyung, Yoon Jong MinAbstract:PURPOSE: A method for wirelessly processing certification using an IP(Internet Protocol) address of a wireless terminal equipped with an IC card or an Application Program is provided to reliably/conveniently process a contract needing the certification/digital signature through wireless Internet connection by storing a certificate that a user is responsible for the certification in the wireless terminal. CONSTITUTION: An IP address agency assigns/offers the IP address to the wireless terminal. The wireless terminal stores the IP address to a memory(720). After connecting to a web server of a client, the wireless terminal transmits the stored IP address to the web server when the web server requests the certification for the client(730). The web server requests the certification to the IP address agency by transmitting the IP address to the IP address agency(735). The IP address agency processes the certification for the client by referring to the IP address received from the web server and transmits certification processing result data to the web server(740).