Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

3.1.5.1 Query a Well-Known LDAP Server for Service Connection Point Objects

Autodiscover server locations can be published in LDAP directories via service connection point objects.

A service connection point object can be created by using the LDAP API specified in [RFC1823] section 4.9.

To discover these servers, Autodiscover clients execute a client search as specified in section 2.2.1.2 and as specified in [RFC1823] section 4.4.

For each of the entries returned, if the serviceBindingInformation attribute is an LDAP URI (a text string of the form "LDAP://"<host>[:<port>] ) and the Keywords attribute contains a string of the form "domain="<domain>, then the client repeats the search as specified in section 2.2.1.2 with the new host element and port element values.

If the serviceBindingInformation attribute is an LDAP URI (a text string of the form "LDAP://"<host>[:<port>] ), but the Keywords attribute does not contain a string of the form "domain="<domain>, then the client repeats the search as specified in section 2.2.1.2 with the new host element and port element values after all other entries have been evaluated.

If the serviceBindingInformation attribute is an "http://" or "https://" URI then the client has found a URI that is possibly an Autodiscover server and the client SHOULD add this to the list of possible Autodiscover servers.

If the Autodiscover directory service map GUID is found in the Keywords, then the serviceBindingInformation is an LDAP URI.

If the Autodiscover URI map GUID is found in the Keywords, then the serviceBindingInformation is an HTTP URI.

Show:
© 2015 Microsoft