Share via

3.5.4 Unregister from ILS

  • Article

Unregistration from an ILS Server by a client is made in three LDAP operations:

  • LDAP Bind

  • LDAP Delete

  • LDAP Unbind

The unregistration process MUST be initiated by making an LDAPBind to an ILS Server. If LDAP v2 is offered, only simple authentication can be used.<27> This is the normally the case when users are located on the Internet. Once a successful Bind has been made, it MUST be followed by an LDAP Delete operation. The Delete operation allows a client to request the removal of an entry from the directory. The Delete operation is as follows:

  • DelRequest: c=-,o=Microsoft, cn=<the email address of the user>,objectClass=rtPerson

This is a modified LDAP entry as per section 2.2.6,  REF _Ref226168721 \h  \* MERGEFORMAT ILS differences from LDAP v3. It has the effect of removing the following two dynamicObjects from the directory:

  • Cn=<the email address of the user>,ou=Dynamic, o=Intranet

    (where the entry type is objectClass=rtPerson, objectClass=dynamicObject).

  • Cn= <the email address of the user>, appName=MS-NetMeeting, ou=Applications, o=Intranet

    (where the entry type is objectClass=rtApplicationUser, objectClass=dynamicObject).

Upon receipt of a Delete Request, the ILS Server MUST attempt to perform the entry removal requested. The result of the Delete Request will be returned to the client in the Delete Response using a standard LDAP response.

The unregister is completed using an LDAP Unbind operation. The function of the Unbind operation is to terminate a protocol session. The Unbind operation has no response defined. Upon transmission of an Unbind request, a protocol client can assume that the protocol session is terminated. Upon receipt of an Unbind Request, a protocol server can assume that the requesting client has terminated the session and that all outstanding requests can be discarded, and can close the connection.