Lines Matching refs:API
33 Service Application Program Interface (GSS-API) Kerberos V5 in the
68 3. Kerberos V5 GSS-API Mechanism ...................................2
85 ([GSS-API]) mechanism [RFC4121]. The authentication sequence is
104 3. Kerberos V5 GSS-API Mechanism
106 The SASL mechanism name for the Kerberos V5 GSS-API mechanism
108 the mechanism is specifically tied to Kerberos V5 and GSS-API's
123 The implementation MAY set any GSS-API flags or arguments not
138 GSS-API mechanism [KRB5GSS], chan_binding of NULL, and targ_name
163 GSS-API implementations that require integ_req_flag to be true. No
216 Kerberos V GSS-API mechanism [KRB5GSS].
237 Identifier (OID) of the Kerberos V5 GSS-API mechanism [KRB5GSS](*).
241 V5 GSS-API mechanism [KRB5GSS].
244 API mechanism as an input parameter. The OID set can be created by
259 verify that the negotiated GSS-API mechanism is indeed Kerberos V5
370 mechanism of GSS-API.
382 and GSS_Accept_sec_context be NULL, hence disallowing use of GSS-API
383 support for channel bindings. GSS-API channel bindings in SASL is
384 expected to be supported via a new GSS-API family of SASL mechanisms
387 Additional security considerations are in the [SASL] and [GSS-API]
388 specifications. Additional security considerations for the GSS-API
414 RFC 2078 [RFC2078] specifies the version of GSS-API used by RFC 2222
416 That version of GSS-API did not provide the integ_integ_avail flag as
420 and as part of moving from RFC 2078 [RFC2078] to RFC 2743 [GSS-API],
431 [GSS-API] Linn, J., "Generic Security Service Application Program
441 [KRB5GSS] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC
457 Interface (GSS-API) Mechanism: Version 2", RFC 4121, July