Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 12
- Abstract
- 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 (ACLs) 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. This memo provides information for the Internet community.
- Publication Date
- 2006-12-01
- Status Note
- Informational
- DOI
10.17487/RFC4768- Link
- https://doi.org/10.17487/RFC4768
- Author(s)
- Sam Hartman
- Keyword(s)
- ACL
Latest version of IETF RFC 4768
Document Versions — IETF RFC 4768
-
▶ IETF RFC 4768 (2006-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Zhu, L., "Generating KDC Referrals to Locate Kerberos Realms" , Work in Progress, June 2006. EXTERNAL
- IETF RFC 2025 [Active*]
- IETF RFC 2743 [Active*]
- IETF RFC 3280 [Superseded*]
- IETF RFC 3281 [Superseded*]
- IETF RFC 4120 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4768.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4768, Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming. Available at https://doi.org/10.17487/RFC4768
Snippet:
IETF RFC 4768, Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming. Available at https://doi.org/10.17487/RFC4768
HTML (ISO 690 compliant)
Preview:
IETF RFC 4768, Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming. Available at https://doi.org/10.17487/RFC4768
Snippet:
<span class="citation"><cite>IETF RFC 4768</cite>, Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming. Available at <a href="https://doi.org/10.17487/RFC4768" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4768</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4768, Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming
doi: 10.17487/RFC4768
url: https://doi.org/10.17487/RFC4768
doi: 10.17487/RFC4768
url: https://doi.org/10.17487/RFC4768
Snippet:
<li> <cite id="bib-rfc4768">IETF RFC 4768</cite>, Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming <span class="doi">10.17487/RFC4768</span> </li>
Referenced By
- IETF RFC 6680 [Active*]