RE: [uddi-spec] Groups - Modeling HTTP Access Authentication in UDDI (uddi-spec-tc-tn-httpauth-20050321.doc) uploaded

[<dave.prout@bt.com>]

I assume this will be covered by Andrew's paper on WS-Security modelling
?

Cheers

Dave
BT 

> -----Original Message-----
> From: Max Voskob [mailto:max.voskob@paradise.net.nz] 
> Sent: 22 March 2005 21:23
> To: uddi-spec@lists.oasis-open.org
> Subject: RE: [uddi-spec] Groups - Modeling HTTP Access 
> Authentication in UDDI 
> (uddi-spec-tc-tn-httpauth-20050321.doc) uploaded
> 
> How do we model other authentication methods, e.g. Kerberos?
> 
> Additional scenarios:
> 
> #1 - a consumer can use the same token for the service as for 
> UDDI if the service and UDDI share the same access control 
> authority (single sing-on).
> 
> #2 - a consumer wants to know where and how obtain the token 
> for the service
> 
> I'm not sure UDDI should be concerned about all this, but it 
> would be useful to get all the information in one place and up-front.
> 
> Cheers,
> Max
> 
> -----Original Message-----
> From: Pete Wenzel [mailto:pete@seebeyond.com]
> Sent: Wednesday, 23 March 2005 3:19 a.m.
> To: hately@us.ibm.com
> Cc: uddi-spec@lists.oasis-open.org
> Subject: Re: [uddi-spec] Groups - Modeling HTTP Access 
> Authentication in UDDI
> (uddi-spec-tc-tn-httpauth-20050321.doc) uploaded
> 
> Andrew, you might wish to update the RFC references.  RFC2617, "HTTP
> Authentication: Basic and Digest Access Authentication", now 
> describes both methods, and obsoletes RFC2069.  RFC2068 (HTTP 
> 1.1) was obsoleted by RFC2616 (but it no longer describes 
> basic auth, so we don't need to reference it for that purpose).
> 
> --Pete
> 
> Thus spoke hately@us.ibm.com (hately@us.ibm.com) on Tue, Mar 
> 22, 2005 at 02:24:53PM -0000:
> > Second Draft.
> > 
> > I Accepted the edit changes, added the keyGenerator, added 
> V3 tModel 
> > structures and added V3 query examples.
> > 
> >  -- Andrew Hately
> > 
> > The document named Modeling HTTP Access Authentication in UDDI
> > (uddi-spec-tc-tn-httpauth-20050321.doc) has been submitted 
> by Andrew 
> > Hately to the OASIS UDDI Specification TC document repository.
> > 
> > Document Description:
> > This document is an OASIS UDDI Technical note that defines 
> a means of 
> > representing that a service uses HTTP Access Authentication
> > 
> > View Document Details:
> > 
> http://www.oasis-open.org/apps/org/workgroup/uddi-spec/document.php?do
> > cument_id=11960
> > 
> > Download Document:  
> > 
> http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.php/11
> > 960/uddi-spec-tc-tn-httpauth-20050321.doc
> > 
> > 
> > PLEASE NOTE:  If the above links do not work for you, your email 
> > application may be breaking the link into two pieces.  You 
> may be able 
> > to copy and paste the entire link address into the address 
> field of your web browser.
> > 
> > -OASIS Open Administration
> 
> --
> Pete Wenzel <pete@seebeyond.com>
> Senior Architect, SeeBeyond
> Standards & Product Strategy
> +1-626-471-6311 (US-Pacific)
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: uddi-spec-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: uddi-spec-help@lists.oasis-open.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: uddi-spec-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: uddi-spec-help@lists.oasis-open.org
> 
>