errata: value for v1.1 and v1.0

2008-01-24 Thread Manger, James H
Errata for OpenID Authentication 2.0 - Final http://openid.net/specs/openid-authentication-2_0.html The values that RPs SHOULD accept for backward compatibility with 1.0 & 1.0 are confusing. The 2.0 spec sometimes talks about …signon/1… URLs: "http://openid.net/signon/1.0"; and "http://openid.net

Re: Integration with Enterprise Directory Services

2008-01-24 Thread Johannes Ernst
Is there a draft available? BTW, why would that be an RFC, as opposed to, say, an OASIS standard (XRI) or an OpenID standard? Because of LDAP? As a "user-centric" technology, I'm not sure that a preferred close relationship to corporate directories -- as opposed to other possible places -- i

Re: Integration with Enterprise Directory Services

2008-01-24 Thread Johannes Ernst
Would you be willing to propose something? On Jan 24, 2008, at 10:11, McGovern, James F (HTSC, IT) wrote: > Would even take it to ensuring that directories use a common OID and > not > just making up their own attribute. Staying equivalent to Cardspace > is a > good thing. > > -Original M

RE: Integration with Enterprise Directory Services

2008-01-24 Thread Drummond Reed
Yes, Marty Schleiff at Boeing is working on an RFC for how to represent XRIs in an LDAP directory for that very reason -- to establish standard OIDs for this attribute. LDAP already has a URI attribute type, but downcasting an XRI into a URI just to squeeze it into that attribute type loses the sem

RE: Integration with Enterprise Directory Services

2008-01-24 Thread McGovern, James F (HTSC, IT)
Would even take it to ensuring that directories use a common OID and not just making up their own attribute. Staying equivalent to Cardspace is a good thing. -Original Message- From: Johannes Ernst [mailto:[EMAIL PROTECTED] Sent: Thursday, January 24, 2008 1:00 PM To: McGovern, James F (

Re: Integration with Enterprise Directory Services

2008-01-24 Thread Johannes Ernst
This doesn't necessarily belong into the core protocol specs, as many implementations will store OpenIDs in places other than directories. However, it would make sense to have a common convention for that ... perhaps a separate 1-page "standard"? On Jan 24, 2008, at 7:02, McGovern, James F (

RE: Integration with Enterprise Directory Services

2008-01-24 Thread McGovern, James F (HTSC, IT)
For CardSpace, MS and other providers store it in the SeeAlso attribute. Figured OpenID in the next rev of the spec should talk more about implementation details. -Original Message- From: Drummond Reed [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 11:57 PM To: McGovern, Ja