[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Action Item 2005-08-23-01: Kerberos Token Profile and RFC1510 vs RFC 4120
Having surveyed the vast array of interop participants I believe we have two possible courses of action; 1. Do nothing. 2. Update the Kerberos Token Profile by making the following changes; a) Add a reference to RFC4120 to Section 5. b) Add 4 URIs to the table in Section 3.2 as follows URI: http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-kerberos-token-p rofile-1.1#Kerberosv5_AP_REQ1510 Description: Kerberos v5 AP-REQ as defined in RFC1510. This ValueType is used when the ticket is an AP Request per RFC1510 URI: http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-kerberos-token-p rofile-1.1#GSS_Kerberosv5_AP_REQ1510 Description: A GSS wrapped Kerberos v5 AP-REQ as defined in the GSSAPI specification. This ValueType is used when the ticket is an AP Request (ST + Authenticator) per RFC1510. URI: http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-kerberos-token-p rofile-1.1#Kerberosv5_AP_REQ4120 Description: Kerberos v5 AP-REQ as defined in RFC4120. This ValueType is used when the ticket is an AP Request per RFC4120 URI: http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-kerberos-token-p rofile-1.1#GSS_Kerberosv5_AP_REQ4120 Description: A GSS wrapped Kerberos v5 AP-REQ as defined in the GSSAPI specification. This ValueType is used when the ticket is an AP Request (ST + Authenticator) per RFC4120. c) Amend the descriptions of the first URI currently in Section 3.2 as follows; URI: http://docs.oasis-open.org/wss/2005/xx/oasis-2005xx-wss-kerberos-token-p rofile-1.1#Kerberosv5_AP_REQ Description: Kerberos v5 AP-REQ as defined in either RFC1510 and RFC4120. This ValueType is used when the ticket is an AP Request. Regards Gudge
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]