LDAP: Unsolicited Notification


LDAP is a request-response protocol with the exception of the unsolicited notification. The unsolicited notification is a transmission from the server to a connected LDAP client. LDAP clients should be prepared to handle the unsolicited notification because the notification is sent when an extraordinary condition has transpired. LDAP clients that do not handle unsolicited notifications risk not receiving important information from the server.

The unsolicited notification is transmitted in the form of an extended response.

Notice of Disconnection

One standardized notification is the notice of disconnection. The object identifier contained in the extended response is 1.3.6.1.4.1.1466.20036, the response value field is absent, and the result code contains the reason for the disconnection.

Aborted Transaction Notification

Transactions provide a notification for aborted transactions.

Example

The class UnsolicitedNotification.java shows how to use the UnboundID LDAP SDK to handle an unsolicited notification.

About Terry Gardner

Terry Gardner was a leading directory services architect with experience with many large scale directory services installations and messaging server installations, and was a Subject Matter Expert in the field of Directory Services and Solaris (operating system) performance. Mr. Gardner also participated in the open-source software community. Mr. Gardner passed away in December, 2013.
This entry was posted in computing, Java, LDAP, UnboundID LDAP SDK and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s