11 messages in org.oasis-open.lists.xri-editorsRE: [xri-editors] LDAP or DSML as loc...| From | Sent On | Attachments |
|---|---|---|
| Wachob, Gabe | Nov 2, 2003 8:27 pm | |
| Drummond Reed | Nov 3, 2003 12:32 am | |
| Wachob, Gabe | Nov 3, 2003 9:01 am | |
| Drummond Reed | Nov 3, 2003 9:57 am | |
| Wachob, Gabe | Nov 3, 2003 10:04 am | |
| Veizades, John | Nov 3, 2003 10:04 am | |
| Wachob, Gabe | Nov 3, 2003 10:16 am | |
| Drummond Reed | Nov 3, 2003 2:58 pm | |
| Wachob, Gabe | Nov 3, 2003 3:02 pm | |
| Drummond Reed | Nov 3, 2003 3:15 pm | |
| Dave McAlpin | Nov 3, 2003 4:08 pm |
| Subject: | RE: [xri-editors] LDAP or DSML as local access protocol | |
|---|---|---|
| From: | Veizades, John (jvei...@visa.com) | |
| Date: | Nov 3, 2003 10:04:59 am | |
| List: | org.oasis-open.lists.xri-editors | |
The way I see local resolution working with LDAP is that instead of doing the HTTP stuff we have defined in the spec you would issue an LDAP_search with the DN set to the entry you are interested and the scope set to LDAP_SCOPE_BASE and the filter function set to objectclass=*. This should return all the attributes for that entry, using the ldap_results call. A couple of cool thing about LDAP when it comes to secure resolution it allows for binding to the LDAP server using standard credentials, it also supports a modification function using the same credentials and finally it is a fairly well understood widely deployed service.
One other note is that DSML is not an access protocol and is used for representing the results of a directory lookup, I don't know if anyone has developed a web services directory access protocol.
John...
-----Original Message----- From: Wachob, Gabe Sent: Monday, November 03, 2003 9:05 AM To: 'Drummond Reed'; XRI Editors (E-mail) Subject: RE: [xri-editors] LDAP or DSML as local access protocol
Well, if you don't define the LDAP query, then you can't have any interoperability and therefore whats the purpose of "defining" an LDAP local access protocol?
To put it concretely, if I have an XRI of "@example/foo.bar", and @example identifies a particular LDAP server, then what LDAP query do I perform? If thats not specified, then a local access protocol binding really hasn't been defined..
-Gabe
-----Original Message----- From: Drummond Reed [mailto:drum...@onename.com] Sent: Monday, November 03, 2003 12:37 AM To: Wachob, Gabe; XRI Editors (E-mail) Subject: RE: [xri-editors] LDAP or DSML as local access protocol
I agree that defining a translation would be useful, but it's not actaully required, is it? Say I have an XRI for "@foo.bar" and then I want to make an LDAP query about a distinguished name at the endpoint identified by "@foo.bar". In that case I don't have to express that distinguished name as an XRI, I just need to know is that LDAP is a supported local access protocol at that endpoint, yes?
=Drummond
-----Original Message----- From: Wachob, Gabe [mailto:gwac...@visa.com] Sent: Sunday, November 02, 2003 8:32 PM To: Drummond Reed; XRI Editors (E-mail) Subject: RE: [xri-editors] LDAP or DSML as local access protocol
Well, thats OK, but there a bit of work to do. We have to define how a XRI gets translated into a LDAP or DSML query. This is not a straightforward process, and there are probably a multitude of ways to do it (an LDAP query is *structured* and I'm not sure how that structure is created).
Does someone have a proposal for how to do this in a flexible way?
-Gabe
-----Original Message----- From: Drummond Reed [mailto:drum...@onename.com] Sent: Friday, October 31, 2003 4:12 PM To: XRI Editors (E-mail) Subject: [xri-editors] LDAP or DSML as local access protocol
Gabe, I forgot that one of my notes in first reading the resolution section was why LDAP or DSML wasn't included as an option alongside X2R as a local access protocol? This is in relation to 3.2.2 an 3.4.
=Drummond
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xri-editors/membe
rs/leave_workgroup.php.
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xri-editors/membe
rs/leave_workgroup.php.
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xri-editors/members/leave_workgroup.php.