Hi, I agree -- the real use case for us involves forwarding tokens too. Best regards, - bill -----Original Message----- From: ogsa-wg-bounces@ogf.org [mailto:ogsa-wg-bounces@ogf.org] On Behalf Of Christopher Smith Sent: Tuesday, July 03, 2007 8:58 AM To: Blair Dillaway; Duane Merrill; ogsa-wg Subject: Re: [ogsa-wg] Updated Express AuthN Profile docs I, for one, am interested in a profile like this. The Kerberos Token Profile seems fine for the authentication step, but one of our main use cases is the forwarding of Kerberos tokens for subsequent use in the environment of jobs and the like, and I don't think the Kerberos Token Profile covers this at all. -- Chris On 02/7/07 14:51, "Blair Dillaway" <blaird@microsoft.com> wrote:
Duane Merrill wrote:
A question for the group: Would it be a good idea to also profile a Kerberos message-level binding assertion policy within the
It might be a good idea and provide value to the community. Before we decide, I think we need to get a better sense of how important a new Kerberos interoperability profile is from the people who deploy and/or provide solutions for organizational grids where Kerberos is already present. If you're in one of these categories, your input would be appreciated.
Are there specific grid scenarios where supporting a Kerberos message authentication option is critical? Do you feel the existing OASIS "Web Services Security Kerberos Token Profile v1.1" specification an adequate basis for grid web services interoperability?
Regards, Blair Dillaway
-- ogsa-wg mailing list ogsa-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-wg
-- ogsa-wg mailing list ogsa-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-wg