H Custom Servlets For The Publisher Channel; Using The Publisher Channel; Authentication; Sampleservlet.java - Novell IDENTITY MANAGER 3.6.1 - MANUAL TASK SERVICE DRIVER Implementation Manual

Manual task service driver implementation
Table of Contents

Advertisement

Custom Servlets for the Publisher
H
Channel
The driver provides an extension mechanism through which additional functionality can be added to
the Publisher channel Web server. Custom servlets can be loaded by the Publisher by specifying the
name of the servlet classes in the Driver configuration item labeled
Section H.1, "Using the Publisher Channel," on page 71
Section H.2, "Authentication," on page 71
Section H.3, "SampleServlet.java," on page 71
H.1 Using the Publisher Channel
If a custom servlet needs to submit data to Identity Manager, the servlet must use the driver's
Publisher channel. The com.novell.nds.dirxml.driver.manualtask.ServletRegistrar and
com.novell.nds.dirxml.driver.manualtask.PublisherData classes are supplied to facilitate this. The
sample code found in

SampleServlet.java

H.2 Authentication

A custom servlet must authenticate users that are submitting information. The sample code found in
SampleServlet.java
illustrates this process. However, the type of authentication performed using the
<check-object-password>
Publisher channel are allowed if the Driver object has rights to perform the changes, regardless of
whether the user submitting the changes has rights or not.
If you are using a URL generated by a command handler on the Subscriber channel, you must use
the com.novell.nds.dirxml.driver.manualtask.URLData class to validate the URL to ensure that the
responder-dn data item has not been tampered with. See the Javadocs for information on
accomplishing this.

H.3 SampleServlet.java

Source code for a sample servlet is included with the driver distribution. The source code is found in
the file
manualtask_driver_docs.zip
The servlet is implemented in the com.novell.nds.dirxml.driver.manualtask.samples.SampleServlet
class.
The sample servlet accepts an HTTP GET request for any resource ending in .sample. The query
string of the HTTP URL must contain a dest-dn item, an attr-name item, and a value item.
The servlet authenticates the user, then submits a modify request to Identity Manager via the driver's
Publisher channel.
illustrates this process.
element does not check eDirectory
in the distribution image.
Additional Servlets
rights. Changes submitted on the
TM
Custom Servlets for the Publisher Channel
H
.
71

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the IDENTITY MANAGER 3.6.1 - MANUAL TASK SERVICE DRIVER and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Identity manager 3.6.1

Table of Contents