Browse Prior Art Database

Generic Security Service Application Program Interface, Version 2 (RFC2078)

IP.com Disclosure Number: IPCOM000002630D
Original Publication Date: 1997-Jan-01
Included in the Prior Art Database: 2019-Feb-16

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Linn: AUTHOR

Related Documents

10.17487/RFC2078: DOI

Abstract

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. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group J. Linn Request for Comments: 2078 OpenVision Technologies Category: Standards Track January 1997 Obsoletes: 1508

Generic Security Service Application Program Interface, Version 2

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.

Abstract

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:

documents defining specific parameter bindings for particular language environments

documents defining token formats, protocols, and procedures to be implemented in order to realize GSS-API services atop particular security mechanisms

This memo revises RFC-1508, making specific, incremental changes in response to implementation experience and liaison requests. It is intended, therefore, that this memo or a successor version thereto will become the basis for subsequent progression of the GSS-API specification on the standards track.

Table of Contents

1: GSS-API Characteristics and Concepts.......................... 3 1.1: GSS-API Constructs.......................................... 6 1.1.1: Credentials.............................................. 6 1.1.1.1: Credential Constructs and Concepts...................... 6 1.1.1.2: Credential Management................................... 7 1.1.1.3: Default Credential Resolution........................... 8

Linn Standards Track [Page 1]

RFC 2078 GSS-API January 1997

1.1.2: Tokens.................................................... 9 1.1.3: Security Contexts........................................ 10 1.1.4: Mechanism Types.......................................... 11 1.1.5: Naming................................................... 12 1.1.6: Channel Bindings......................................... 14 1.2: GSS-API Features and Issues................................ 15 1.2.1: Status Reporting......................................... 15 1.2.2: Per-Message Security Service Availability................. 17 1.2.3: Per-Message Replay Detection and Sequencing............... 18 1.2.4: Quality of Protection.................................... 20 1.2.5: Anonymity Support......................................... 21 1.2.6: Initialization............................................ 22 1.2.7: Per-Message Protection During Context Establishment....... 22 1.2.8...

Processing...
Loading...