OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wss] Issue #283 - Kerberos User to User Protocol

I asssume that the that token format described equally applies to request and response messages.

Anthony Nadalin | work 512.838.0085 | cell 512.289.4122
Inactive hide details for "Hal Lockhart" <hlockhar@bea.com>"Hal Lockhart" <hlockhar@bea.com>

          "Hal Lockhart" <hlockhar@bea.com>

          06/09/2004 11:28 AM





[wss] Issue #283 - Kerberos User to User Protocol

Really everything has been said before on the list. I will summarize.

It was proposed that there was no reason for a binary token to carry a Ticket Granting Ticket (TGT) in the context of WSS. Frank pointed out that it was required for the User to User U2U) protocol. The client sends its TGT to the Server, which forwards it along with its own TGT to the KDC. The KDC makes up a special service ticket based on both TGTs, which allows the client and server to share a session key, without the server having to keep the long term secret on disk (at the cost of extra messages).

The main problem with U2U is that although the need for it depends on the configuration of the server (typed in password vs. keytab) it is not transparent to the client. Without some advertisement or negotiation protocol, this requires prior agreement. However, the use of U2U in WSS is at least conceivable, therefore it should be allowed.

Resolution: Same as agreed under Issue #277 - leave TGT as an option, provide text explaining the rationale.


To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to

GIF image

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]