Drummond Reed wrote:
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
Is there merit in also defining other aspects such as how the OP would
store history in LDAP by defining new ObjectClass?
*
This communication, including attachments, is
for the exclusive use of addressee and may contain
To: McGovern, James F (HTSC, IT)
Cc: specs@openid.net
Subject: Re: Integration with Enterprise Directory Services
James,
It appears you possess a good amount of knowledge on this topic.
I believe that if you were to come up with some preliminary
implementation guidelines (and presented them
Reed
Subject: RE: Integration with Enterprise Directory Services
The process to get an OID issued under the directory OID includes doing
an RFC.
The old draft (haven't touched it for about a year) can be seen at
various URLs. Here's one:
http://opends.org/source/xref/trunk/www/public
, James F (HTSC, IT); specs@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
PM
To: McGovern, James F (HTSC, IT); specs@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
(HTSC, IT)
Cc: specs@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
10:12 AM
To: Johannes Ernst
Cc: specs@openid.net
Subject: RE: Integration with Enterprise Directory Services
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 (HTSC, IT)
Cc: specs@openid.net
Subject: Re: Integration with Enterprise Directory Services
This doesn't necessarily belong into the core protocol specs, as many
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf
Of McGovern, James F (HTSC, IT)
Sent: Thursday, January 24, 2008 10:12 AM
To: Johannes Ernst
Cc: specs@openid.net
Subject: RE: Integration with Enterprise Directory Services
Would even take it to ensuring that directories use a common
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
] On Behalf
Of McGovern, James F (HTSC, IT)
Sent: Wednesday, January 23, 2008 1:47 PM
To: specs@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
12 matches
Mail list logo
