Integration with Enterprise Directory Services

[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:jernst+openid.net at netmesh.us] 
Sent: Thursday, January 24, 2008 1:00 PM
To: McGovern, James F (HTSC, IT)
Cc: specs at openid.net
Subject: Re: Integration with Enterprise Directory Services

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 (HTSC, IT) wrote:

> 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:drummond.reed at cordance.net]
> Sent: Wednesday, January 23, 2008 11:57 PM
> To: McGovern, James F (HTSC, IT); specs at openid.net
> Subject: RE: Integration with Enterprise Directory Services
>
> James, are you asking about the recommended format for saving an 
> OpenID identifier in an LDAP directory? If so, I know Boeing has done 
> some work in that area -- I can check with their directory guru.
>
> =Drummond
>
>> -----Original Message-----
>> From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On 
>> Behalf Of McGovern, James F (HTSC, IT)
>> Sent: Wednesday, January 23, 2008 1:47 PM
>> To: specs at openid.net
>> Subject: Integration with Enterprise Directory Services
>>
>> What is the standard recommendation for how identifiers get stored in

>> enterprise directory services (e.g. LDAP)?
>>
>>
>>
>> *********************************************************************
>> *
>> *** This communication, including attachments, is for the exclusive 
>> use of addressee and may contain proprietary, confidential and/or 
>> privileged information.  If you are not the intended recipient, any 
>> use, copying, disclosure, dissemination or distribution is strictly 
>> prohibited.  If you are not the intended recipient, please notify the

>> sender immediately by return e-mail, delete this communication and 
>> destroy all copies.
>> *********************************************************************
>> *
>> ***
>>
>> _______________________________________________
>> specs mailing list
>> specs at openid.net
>> http://openid.net/mailman/listinfo/specs
>
>
>
> **********************************************************************
> *** This communication, including attachments, is for the exclusive 
> use of addressee and may contain proprietary, confidential and/or 
> privileged information.  If you are not the intended recipient, any 
> use, copying, disclosure, dissemination or distribution is strictly 
> prohibited.  If you are not the intended recipient, please notify the 
> sender immediately by return e-mail, delete this communication and 
> destroy all copies.
> **********************************************************************
> ***
>
> _______________________________________________
> specs mailing list
> specs at openid.net
> http://openid.net/mailman/listinfo/specs



*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************