Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
This guides is a reference to the document type definitions (DTD) that Identity Manager uses. The
guide contains definitions for each of the elements used in Identity Manager. There are separate
DTDs for different components of Identity Manager.
“Filter DTD” on page 15
“NDS DTD” on page 23
“Map DTD” on page 161
“DirXML Script DTD” on page 169
“DirXML Entitlements DTD” on page 497
“Jobs DTD” on page 531
Audience
novdocx (en) 13 May 2009
This guide is intended as a reference for Identity Manager consultants.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of the Identity Manager DTD Reference, and the latest Identity Manager
documentation, visit the Identity Manager Documentation Web site (http://www.novell.com/
documentation/idm36/).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
®
A trademark symbol (
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux or UNIX, should use forward slashes as required by your software.
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
About This Guide11
novdocx (en) 13 May 2009
12Identity Manager 3.6 DTD Reference
1
DTD Overview
This guides is a reference for the Identity Manager document type definitions (DTD). There are
separate DTDs for different components of Identity Manager:
“Filter DTD” on page 15
“NDS DTD” on page 23
“Map DTD” on page 161
“DirXML Script DTD” on page 169
“DirXML Entitlements DTD” on page 497
“Jobs DTD” on page 531
What’s New in Identity Manager 3.6.1
Version 3.6.1 of DTD has no new features.
novdocx (en) 13 May 2009
1
What’s New in Identity Manager 3.6
Added Jobs DTD section that provides introductory information about the XML structure used
to create scheduled Jobs in Identity Manager.
Added do-add-role and do-remove-role.
Changed do-send-email-from-template to allow sending html content from policy.
Made attribute
Changed do-find-matching-object to set a local variable if they encounter an error and provide
additional information in the server log.
Added
Added optional
Added optional
offset
policy-dn
and
default-value
old-password
optional for token-generate-password.
offset-unit
attribute to token-convert-time.
attribute to token-map.
attribute to do-set-src-password and do-set-dest-password.
DTD Overview
13
novdocx (en) 13 May 2009
14Identity Manager 3.6 DTD Reference
2
Filter DTD
An Identity Manager filter is primarily for controlling which object classes are synchronized and
which attributes are synchronized for those object classes. Additionally, other behaviors of those
classes and attributes within Identity Manager are controlled through the filter.
An Identity Manager filter consists of a top level <filter> element that contains a set of <filter-class>
elements, each of which contains a set of <filter-attr> elements. The filter for a particular driver is
stored in the DirXML-DriverFilter attribute on the DirXML-Driver object.
See “Filter Elements” on page 15 for a list of all the elements in the Filter DTD.
2.1 Filter Elements
ElementDescription
novdocx (en) 13 May 2009
2
filterFilter for an Identity Manager driver.
filter-attrBehavior of an attribute for a particular object class.
filter-classBehavior of an object class.
Filter DTD
15
filter
Consists of a set of <filter-class> elements that describe the object classes used by a particular
instance of an Identity Manager driver.
Describes an attribute of the enclosing <filter-class> that is used by a particular instance of an
Identity Manager driver. The attr-name attribute specifies the name of an attribute in
eDirectory
on the respective channels according to the following table. If the channel setting for the object class
as a whole is ignored, then the setting for individual attributes is ignored.
Remarks
The publisher and subscriber attributes control whether this attribute is synchronized on the
respective channels according to the following table. If the channel setting for the object class as a
whole is ignored, then the setting for individual attributes is ignored.
ValueDescription
ignoreChanges to this attribute are not reported or
TM
.The publisher and subscriber attributes control whether this attribute is synchronized
automatically synchronized.
novdocx (en) 13 May 2009
notifyChanges to this attribute are reported but not
automatically synchronized.
syncChanges to this attribute are reported and
automatically synchronized.
resetChanges to this attribute are reported and triggers
the attribute to be automatically reset to the values
from the other channel. It is illegal for both
Publisher and Subscriber to reset for the same
attribute.
The merge-authority attribute controls the behavior of the attribute during a merge operation
according to the following table:
18Identity Manager 3.6 DTD Reference
ValueBehaviorValid
novdocx (en) 13 May 2009
default1. If an attribute is not being synchronized in either
channel, then no merging occurs.
2. If an attribute is being synchronized in one
channel and not the other, then all existing values
on the destination for that channel are removed and
replaced with the values from the source for that
channel. If the source has multiple values and the
destination can only accommodate a single value,
then only one of the values is used on the
destination side, although it is undefined which of
those values are used.
3. If an attribute is being synchronized in both
channels and both sides can accommodate
multiple values, then each side ends up with the
union of values present on either side.
4. If an attribute is being synchronized in both
channels and both sides can accommodate only a
single value, the application ends up with the value
from eDirectory unless there is no value in
eDirectory. In this case eDirectory ends up with the
value from the application (if any).
5. If an attribute is synchronized in both channels
and only one side can accommodate multiple
values then the single-valued side's value is added
to the value from the multiple-value side if it is
already there. If there is no value on the singlevalued side one of the values (undefined) is added
to the single-valued side.
Always
edirHas the same behavior as the default if the
attributes are synchronized on the Subscriber
channel and not on the Publisher channel.
appHas the same behavior as the default if the
attributes are synchronized on the Publisher
channel and not on the Subscriber channel.
noneNo merging occurs regardless of synchronization. Always
When synchronizing or notifying
on the Subscriber channel
When synchronizing or notifying
on the Publisher channel
The publisher-optimize-modify attribute controls whether or not changes to this attribute are
examined on the Publisher channel to determine the minimal change needed in the Identity Vault.
Example
See <filter>.
Allowed Content
EMPTY
Filter DTD19
Attributes
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
attr-nameCDATA
Name of the attribute.
merge-authority default | edir | app | none
Flag that controls how this
attribute is merged.
publisherignore | notify | sync | reset
Flag that controls Publisher
channel synchronization.
publisher-optimize-modifytrue | false
Flag that controls optimization of
modifications on the Subscriber
channel.
subscriberignore | notify | sync | reset
Flag that controls Subscriber
channel synchronization.
Content Declaration
Empty
#REQUIRED
default
ignore
true
ignore
Parent Elements
ElementDescription
filter-classBehavior of an object class.
20Identity Manager 3.6 DTD Reference
filter-class
Describes an object class that is used by a particular instance of an Identity Manager driver. The
class-name attribute specifies the name of an effective (that is, structural or base) class in eDirectory
and only applies to objects that have that particular base class.
Remarks
The Publisher and Subscriber attributes control whether this class is synchronized on the respective
channels.
ValueDescription
ignoreChanges to the objects of this class are not reported or
automatically synchronized.
syncChanges to the objects of this class are reported and automatically
synchronized.
novdocx (en) 13 May 2009
The publisher-track-template-member attribute controls whether or not the Publisher channel
maintains the Member of Template attribute when it creates objects from a template. The publisher-
®
create-homedir attribute controls whether or not a NetWare
home directory is automatically
created when a User is created with the Home Directory attribute populated.
Example
See <filter>.
Allowed Content
ElementDescription
filter-attr Behavior of an attribute for a particular object class.
Attributes
AttributePossible ValuesDefault Value
class-nameCDATA
#REQUIRED
Name of the object class.
publisherignore | sync
Flag that controls Publisher
channel synchronization.
ignore
Filter DTD21
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
publisher-create-homedirtrue | false
Flag that controls automatic
creation of home directories.
publisher-track-template-member true | false
Flag that controls the tracking of
objects.
subscriberignore | sync
Flag that controls Publisher
channel synchronization.
true
false
ignore
Content Rule
filter-attr
Parent Elements
ElementDescription
filterFilter for an Identity Manager driver.
22Identity Manager 3.6 DTD Reference
3
NDS DTD
novdocx (en) 13 May 2009
3
The NDSTM document type definition file (
the Identity Manager engine can process. XML documents that do not conform to this schema
generate errors.
nds.dtd
The
Input and output commands and events (such as add, delete, modify, and rename) that can be
performed on entries and the data that must be included with each.
subscriber-stateDriver SubscriptionShim state information.
syncResynchronization or migrate event.
templateSpecifies a template. Deprecated as of Identity
Manager 2.0.
userThe authentication user name
valueThe attribute value.
26Identity Manager 3.6 DTD Reference
add
Used as an event notification from the PublicationShim to Identity Manager when an object is added
in the application. When it is used as a notification, an <association> is required. It is also used as a
command from Identity Manager to the SubsciptionShim to add an object in the application.
Remarks
<add> contains an <add-attr> for each attribute of the object added.
<add> might contain a <password> for the object added.
A response to <add> should be a <status> indicating whether or not the <add> was processed
successfully. When used as a command, <add> should also return an <add-association> that
contains the unique key for the newly added object. The dest-dn and dest-entry-id attributes of the
<add-association> should be set to the src-dn and src-entry-id of the <add>.
The name of the base class of the
object. The class name is
mapped between the application
and eDirectory namespaces by
the Schema Mapping policy so
that Identity Manager sees the
name in the eDirectory
namespace and a driver sees the
name in the application
namespace.
dest-dn CDATA
The distinguished name of the
target object in the namespace of
the receiver.
Should be left empty for event
notifications. Filled in by the
Placement policy on commands.
dest-entry-id CDATA
The entry ID of the target object
in the namespace of the receiver.
Reserved. Should be ignored by
the driver.
TM
#REQUIRED
#IMPLIED
#IMPLIED
event-id CDATA
An identifier used to tag the
results of an event or command.
Should be copied to the event-id
attribute of the resulting <status>
and <add-association> elements.
qualified-src-dn CDATA
The qualified version of src-dn.
Only used for describing objects
from eDirectory.
src-dn CDATA
The distinguished name of source
object that generated the event in
the namespace of the sender.
Should be copied to the dest-dn
attribute of the resulting <add-
association> for commands.
#IMPLIED
#IMPLIED
#IMPLIED
28Identity Manager 3.6 DTD Reference
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
src-entry-id CDATA
The entry ID of source object that
generated the event in the
namespace of the sender.
Should be copied to the destentry-id attribute of the resulting
<add-association> for
commands.
template-dn CDATA
The distinguished name of a
template in the receiver's
namespace to use as a basis for
creating the object.
Filled in by the Create policy for
commands. Drivers only need to
implement this if it makes sense
for the application.
The distinguished name of the
target object in the namespace of
the receiver.
Should be set to the src-dn of the
<add>.
dest-entry-id CDATA
The entry id of the target object in
the namespace of the receiver.
Should be set to the src-entry-id
of the <add>.
event-id CDATA
An identifier used to tag the
results of an event or command.
Should be set to the event-id of
the <add>.
#REQUIRED
#IMPLIED
#IMPLIED
Content Rule
( #PCDATA | operation-data ) *
30Identity Manager 3.6 DTD Reference
Parent Elements
ElementDescription
inputInput events or commands.
outputResults of events or commands.
novdocx (en) 13 May 2009
NDS DTD31
add-attr
Used to specify the attribute values for an <add> operation or event. Each <add-attr> should contain
at least one <value>
Example
See <add>.
Allowed Content
ElementDescription
valueThe attribute value.
Attributes
novdocx (en) 13 May 2009
AttributePossible ValuesDefault Value
attr-name CDATA
The name of the attribute.
The name is mapped between
the application and eDirectory
namespaces by the Schema
Mapping policy so that Identity
Manager sees the name in the
eDirectory namespace and a
driver sees the name in the
application namespace. The
mapping rule uses the class
name attribute of the enclosing
command or event to determine
which class to use for mapping
the attribute name.
enforce-password-policytrue | false
Reserved. Should be ignored by
the driver.
#REQUIRED
#IMPLIED
Content Rule
( value + )
32Identity Manager 3.6 DTD Reference
Parent Elements
ElementDescription
addAdds an object when an add event occurs.
novdocx (en) 13 May 2009
NDS DTD33
add-value
Used to specify values added to the attribute specified in the enclosing <modify-attr>. A driver
should gracefully ignore an <add-value> for a value that already exists and continue to process the
remainder of the enclosing <modify>.
Example
See <modify>.
Allowed Content
ElementDescription
value The attribute value.
novdocx (en) 13 May 2009
Attributes
None
Parent Elements
ElementDescription
modify-attrModifies an attribute.
34Identity Manager 3.6 DTD Reference
allow-attr
Used to specify attributes that are allowed in the event filter for the class specified in the enclosing
<allow-class>.
Example
See <init-params>.
Allowed Content
EMPTY
Attributes
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
attr-name CDATA
The name of the attribute.
The name is mapped between
the application and
eDirectorynamespaces by the
Schema Mapping policy so that
Identity Manager sees the name
in the eDirectory namespace and
a driver sees the name in the
application namespace. The
mapping rule uses the class
name attribute of the enclosing
command or event to determine
which class to use for mapping
the attribute name.
is-sensitive true | false
If true, specifies that the attribute
values referenced by the <allow-
attr> element contain sensitive
data that should be suppressed in
trace information.
Content Declaration
#REQUIRED
false
Empty
NDS DTD35
Parent Elements
ElementDescription
allow-classAllow a class in the filter.
novdocx (en) 13 May 2009
36Identity Manager 3.6 DTD Reference
allow-class
Used to specify classes that are allowed in the event filter specified by the enclosing <driver-filter>.
Example
See <init-params>.
Allowed Content
ElementDescription
allow-attrAllow an attribute in the filter.
Attributes
novdocx (en) 13 May 2009
AttributePossible ValuesDefault Value
class-name CDATA
The name of the base class of the
object.
The class name is mapped
between the application and
eDirectory namespaces by the
Schema Mapping policy so that
Identity Manager sees the name
in the eDirectory namespace and
a driver sees the name in the
application namespace.
#REQUIRED
Content Rule
( allow-attr ) *
Parent Elements
ElementDescription
driver-filterPublication and Subscription class and attribute
event filter.
NDS DTD37
app-name
Used to specify a class or attribute name in the application namespace.
Example
See <attr-name-map>.
Allowed Content
#PCDATA
Attributes
None
Content Rule
novdocx (en) 13 May 2009
( #PCDATA )
Parent Elements
ElementDescription
attr-nameMaps an attribute name.
class-nameMaps a class name.
38Identity Manager 3.6 DTD Reference
association
Used to specify the unique key of an application object that is the source of an event notification
from the PublicationShim to Identity Manager, the target of a command sent form Identity Manager
to the SubscriptionShim, or the base object of a <query> sent to the SubscriptionShim.
check-object-passwordChecks the password against an eDirectory object.
deleteDeletes an object when a delete event occurs.
instanceCurrent state of an instance of an object.
modifyModifies an object when a modify event occurs.
modify-associationModifies an association command.
modify-passwordModifies an object password when a modify event
for a password occurs.
moveMoves an object when a move event occurs.
NDS DTD39
ElementDescription
parentThe parent container of an object.
query Query command.
query-exQuery command with a result count limit.
renameRenames an object when a rename event occurs.
syncResynchronization or migrate event.
novdocx (en) 13 May 2009
40Identity Manager 3.6 DTD Reference
attr
Used to specify the attribute values for the object specified by the enclosing <instance>. Each <attr>
should contain at least one <value>.
Example
See <instance>.
Allowed Content
ElementDescription
value The attribute value.
Attributes
novdocx (en) 13 May 2009
AttributePossible ValuesDefault Value
attr-name CDATA
The name of the attribute.
The name is mapped between
the application and eDirectory
namespaces by the Schema
Mapping policy so that Identity
Manager sees the name in the
eDirectory namespace and a
driver sees the name in the
application namespace. The
mapping rule uses the class
name attribute of the enclosing
command or event to determine
which class to use for mapping
the attribute name.
#REQUIRED
Content Rule
( value * )
Parent Elements
ElementDescription
instanceCurrent state of an instance of an object.
NDS DTD41
attr-def
Used to specify a schema attribute for the class specified by the enclosing <class-def>.
Example
See <schema-def>.
Allowed Content
EMPTY
Attributes
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
asn1id CDATA
The ASN.1 Object ID of the
attribute.
attr-name CDATA
The name of the attribute.
case-sensitive true | false
Whether or not the attribute is
case sensitive.
multi-valued true | false
Whether or not the attribute can
hold more than one value
naming true | false
Whether or not the attribute can
be used as part of the RDN of an
object of the enclosing class.
read-only true | false
Whether or not the attribute is
read-only.
#IMPLIED
#REQUIRED
false
true
false
false
required true | false
42Identity Manager 3.6 DTD Reference
false
Whether or not the attribute is
required by an object of the
enclosing class.
Used to specify a mapping between an attribute name in the eDirectory namespace and the
application namespace.
Example
See <attr-name-map>.
Allowed Content
ElementDescription
nds-nameName in the eDirectory namespace. The names
specified must be unique for the given class.
app-nameName in the application namespace. The names
specified must be unique for the given class.
novdocx (en) 13 May 2009
Attributes
AttributePossible ValuesDefault Value
class-name CDATA
The name of the class that this
attribute name mapping is for in
the eDirectory namespace. If
missing or blank then mapping is
considered generic and applies to
all classes that don't have a
class-specific mapping.
#IMPLIED
Content Rule
( nds-name , app-name )
Parent Elements
ElementDescription
attr-name-mapTop-level element for Schema Mapping policies.
44Identity Manager 3.6 DTD Reference
attr-name-map
The top-level (document) element for Schema Mapping policies. Schema Mapping policies are
stored in the DirXML-XmlData attribute of a DirXML-Rule object that is pointed to by the
DirXML-MappingRule attribute of a DirXML-Driver object.
Remarks
<attr-name-map> contains <attr-name> and <class-name> elements that specify a one-to-one
mapping between class and attribute names in eDirectory and the application namespace. Schema
Mapping policies are applied to map from the eDirectory namespace to the application namespace
whenever XML is sent or returned from Identity Manager to the driver and before the Output
transform is applied.
Schema Mapping policies are applied to map from the application namespace to the eDirectory
namespace whenever XML is sent or returned from driver to Identity Manager after the Input
Transform policy is applied.
Schema Mapping policies try to map the <class-name> and <attr-name> attributes of all elements in
the document. The <class-name> to map an attribute name is found by looking the nearest ancestor
element with a <class-name> attribute.
novdocx (en) 13 May 2009
Example
<attr-name-map>
<!-- map eDirectory class User application class inetOrgPerson
-->
<class-name>
<nds-name>User</nds-name>
<app-name>inetOrgPerson</app-name>
</class-name>
<!-- map NDS attribute Given Name to application attribute givenName
for class User -->
<attr-name class-name="User">
<nds-name>Given Name</nds-name>
<app-name>givenName</app-name>
</attr-name>
<!-- map NDS attribute Surname to application attribute sn for all
classes -->
<!-- that don't have a class-specific mapping -->
<attr-name>
<nds-name>Surname</nds-name>
<app-name>sn</app-name>
</attr-name>
</attr-name-map>
Allowed Content
ElementDescription
attr-nameMaps an attribute name.
NDS DTD45
ElementDescription
class-nameMaps a class name.
Attributes
None
Content Rule
( attr-name | class-name ) *
Parent Elements
None
novdocx (en) 13 May 2009
46Identity Manager 3.6 DTD Reference
authentication-info
Used to specify the parameters needed for the driver to connect to and authenticate to an application
server.
Example
See <init-params>.
Allowed Content
ElementDescription
serverThe authentication server.
userThe authentication username.
passwordThe authentication password.
novdocx (en) 13 May 2009
Attributes
None
Content Rule
( server ? , user ? , password ? )
Parent Elements
ElementDescription
init-paramsInitialization parameters for the DriverShim,
SubscriptionShim, or PublicationShim.
NDS DTD47
check-object-password
Used to validate a password against an eDirectory object. A <status> result is returned indicating
success or failure.
Remarks
An <association> element, a dest-dn attribute, or a dest-entry-id attribute is used to specify the
eDirectory object against which the password is to be checked.
If the eDirectory object's Login Disabled attribute is set to true, then the <status> indicates an error
even if the password is correct.
Used to specify a schema class the enclosing <schema-def>.
Example
See <schema-def>.
Allowed Content
ElementDescription
attr-defSchema attribute definition.
Attributes
novdocx (en) 13 May 2009
AttributePossible ValuesDefault Value
asn1id CDATA
The ASN.1 Object ID of the class.
class-name CDATA
The name of the schema class.
container true | false
Whether or not an object of this
class can be a container for other
objects.
#IMPLIED
#REQUIRED
false
Content Rule
( attr-def ) *
Parent Elements
ElementDescription
schema-defSchema definition.
NDS DTD51
class-name
Used to specify a mapping between a class name in the eDirectory namespace and the application
namespace.
Example
See <attr-name-map>.
Allowed Content
ElementDescription
nds-nameName in the eDirectory namespace. The names
specified must be unique to this <class-name>.
app-nameName in the eDirectory namespace. The names
specified must be unique to this <class-name>.
novdocx (en) 13 May 2009
Attributes
None
Content Rule
( nds-name , app-name )
Parent Elements
ElementDescription
attr-name-mapTop-level element for Schema Mapping policies.
52Identity Manager 3.6 DTD Reference
component
Used to specify an individual field of the enclosing <value> if the data type of the value is
structured.
Example
See <value>.
Allowed Content
#PCDATA
Attributes
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
association-ref CDATA
The association value
(application object unique key) of
the object being referenced by
this component. This is required
on all components that refer to
other objects when the
component is part of a notification
event from the driver. This exists
on all components that refer to
other objects when the
component is part of a command
from Identity Manager if the
referenced object has an
established association in
eDirectory.
name CDATA
The name of the component. This
is specific to individual attribute
syntaxes. See <value>.
Content Rule
#IMPLIED
#REQUIRED
( #PCDATA )
Parent Elements
ElementDescription
valueThe attribute value.
NDS DTD53
config-object
Used to specify objects and attributes where additional configuration information is obtained.
Remarks
During driver startup, the contained <query> is processed and the resulting <instance> element
replaces the <config-object> in the <init-params> passed to the DriverShim.init(),
SubscriptionShim.init(), and PublicationShim.init() methods.
Example
See <init-params>.
Allowed Content
novdocx (en) 13 May 2009
ElementDescription
query Query command.
Attributes
AttributePossible ValuesDefault Value
display-name CDATA
The name to display in the
interface generated by
ConsoleOne
®
.
#IMPLIED
Content Rule
( query )
Parent Elements
None
54Identity Manager 3.6 DTD Reference
contact
Used to specify the point of contact for the creator of the enclosing document.
Example
See <nds>.
Allowed Content
#PCDATA
Attributes
None
Content Rule
novdocx (en) 13 May 2009
#PCDATA
Parent Elements
ElementDescription
sourceThe source or creator of the document.
NDS DTD55
copy-attr
Deprecated as of Identity Manager 2.0. Use DirXMLScript <token-op-attr> instead.
Remarks
<copy-attr> is used as a token to specify a string replacement in the distinguished name generated by
the enclosing <placement>.
The replacement string is generated by copying the first value for the attribute specified by attrname from the <add> event that is being processed. If the attribute does not exist, then the enclosing
<placement-rule> is skipped. Structured attribute types are not supported.
Example
See <placement-rules>.
Allowed Content
novdocx (en) 13 May 2009
EMPTY
Attributes
AttributePossible ValuesDefault Value
attr-name CDATA
The name of the attribute.
The name is mapped between
the application and eDirectory
namespaces by the Schema
Mapping policy so that Identity
Manager sees the name in the
eDirectory namespace and a
driver sees the name in the
application namespace. The
mapping rule uses the class
name attribute of the enclosing
command or event to determine
which class to use for mapping
the attribute name.
#REQUIRED
Content Declaration
Empty
56Identity Manager 3.6 DTD Reference
Parent Elements
ElementDescription
placementObject placement specifier. Deprecated as of
Identity Manager 2.0.
novdocx (en) 13 May 2009
NDS DTD57
copy-name
Deprecated as of Identity Manager 2.0. Use DirXMLScript <token-src-dn> instead.
Remarks
<copy-name> is used as a token to specify a string replacement in the distinguished name generated
by the enclosing <placement>.
The replacement string is generated by copying the unqualified portion of the leaf-most component
of the src-dn attribute from the <add> event that is being processed. If the src-dn does not exist, then
the enclosing <placement-rule> is skipped.
Example
See <placement-rules>.
Allowed Content
novdocx (en) 13 May 2009
EMPTY
Attributes
None
Content Declaration
Empty
Parent Elements
ElementDescription
placementObject placement specifier. Deprecated as of
Identity Manager 2.0.
58Identity Manager 3.6 DTD Reference
copy-path
Deprecated as of Identity Manager 2.0. Use DirXMLScript <token-src-dn> instead.
Remarks
<copy-path> is used as a token to specify a string replacement in the distinguished name generated
by the enclosing <placement>.
The replacement string is generated by copying the src-dn attribute from the <add> event that is
being processed. A conversion from the src-dn-format to the dest-dn-format of the enclosing
<placement-rules> is performed if the formats are different. Conversion from a typeless
(unqualified) format to a typed (qualified) format is unsupported unless the source is eDirectory.
Example
See <placement-rules>.
novdocx (en) 13 May 2009
Allowed Content
EMPTY
Attributes
None
Content Declaration
Empty
Parent Elements
ElementDescription
placementObject placement specifier. Deprecated as of
Identity Manager 2.0.
NDS DTD59
copy-path-suffix
Deprecated as of Identity Manager 2.0. Use DirXMLScript <token-unmatched-src-dn> instead.
Remarks
<copy-path-suffix> is used as a token to specify a string replacement in the distinguished name
generated by the enclosing <placement>.
The replacement string is generated by copying src-dn attribute from the <add> event that is being
processed, and then stripping away the portion of the src-dn matched by a <match-path> in the
enclosing <placement-rule>. If no <match-path> was specified then the whole src-dn is copied. A
conversion from the src-dn-format to the dest-dn-format of the enclosing <placement-rules> is
performed if the formats are different. Conversion from a typeless (unqualified) format to a typed
(qualified) format is unsupported unless the source is eDirectory.
Example
novdocx (en) 13 May 2009
See <placement-rules>.
Allowed Content
EMPTY
Attributes
None
Content Declaration
Empty
Parent Elements
ElementDescription
placementObject placement specifier. Deprecated as of
Identity Manager 2.0.
60Identity Manager 3.6 DTD Reference
create-rule
Deprecated as of Identity Manager 2.0. Use DirXMLScript <rule> instead.
Remarks
<create-rule> is used to specify the criteria for creating a new object as a result of an <add> event.
When a <create-rule> is evaluated, it first checks whether or not this is a suitable rule for the <add>
event in question. It does this by checking if a class name is specified by the rule. If so, the rule is
only suitable if the class name matches the class name on the event. It then checks if any <match-
attr> criteria are specified by the rule. If so, the rule is only suitable if the <add> contains all the
attribute values required by the <match-attr>. If a rule is determined to not be suitable, it is skipped.
When a suitable rule is found, the <add> is evaluated to see if it has a value for all of the <required-
attr> that do not contain a default value. If not, the <add> is vetoed; otherwise, it is allowed. Then
any required attributes with default values that were missing from the <add> are filled in. If the
write-back attribute of the <required-attr> element is set, the missing values are also written back to
the source object. The template-dn attribute is filled in if a <template> is specified.
novdocx (en) 13 May 2009
Example
See <create-rules>.
Allowed Content
ElementDescription
match-attrMatches an attribute. Deprecated as of Identity
Manager 2.0.
read-attr Required attribute. Deprecated as of Identity
Manager 2.0.
templateSpecifies a template. Deprecated as of Identity
Manager 2.0.
Attributes
AttributePossible ValuesDefault Value
class-nameCDATA
#IMPLIED
The name of the base class of the
objects this rule applies to in the
eDirectory namespace. If empty
or not present, then this rule
applies to all base classes
NDS DTD61
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
description CDATA
Description of this rule, primarily
for use in ConsoleOne.
#IMPLIED
Content Rule
( match-attr * , required-attr * , template ? )
Parent Elements
ElementDescription
create-rulesTop-level element for object creation rules.
Deprecated as of Identity Manager 2.0.
62Identity Manager 3.6 DTD Reference
create-rules
Deprecated as of Identity Manager 2.0. Use DirXMLScript <policy> instead.
Remarks
<create-rules> is the top-level (document) element for object creation rules. Object creation rules
are stored in the DirXML-XmlData attribute of a DirXML-Rule object that is pointed to by the
DirXML-CreateRule attribute of a DirXML-Subscriber or DirXML-Publisher object.
In the Subscriber channel, the source is eDirectory, and the destination is the application. In the
Publisher channel, the source is the application and the destination is eDirectory.
Object creation rules are used to determine whether or not to create a new object in the destination as
a result of an <add> event in the source. (Identity Manager automatically converts <modify> into
<add> for events from unassociated objects). Object creation rules are applied only after any
existing Matching rules are applied and fail to find a matching object in the destination.
<create-rules> contains 0 or more <create-rule> elements. The creation rule processor evaluates
each <create-rule> in order until a suitable rule is found. That rule then vetoes or allows the object
creation and fills in any default attributes and templates specified. If no suitable <create-rule> is
found, then the object creation is allowed.
novdocx (en) 13 May 2009
Example
<create-rules>
<!-- For all Users in the Defense organization require Given Name-->
<!-- Surname, and Security Clearance. Create using the -->
<!-- templates\Secure User template -->
<create-rule class-name="User">
<match-attr attr-name="OU">
<value>Defense</value>
</match-attr>
<required-attr attr-name="Given Name"/>
<required-attr attr-name="Surname"/>
<required-attr attr-name="Security Clearance"/>
<template template-dn="templates\Secure User"/>
</create-rule>
<!-- For all other Users require Given Name and Surname. -->
<!-- Default the value of Security Clearance to None -->
<!-- Don't use a template for creation -->
<create-rule class-name="User">
<required-attr attr-name="Given Name"/>
<required-attr attr-name="Surname"/>
<required-attr attr-name="Security Clearance">
<value>None</value>
</required-attr>
</create-rule>
</create-rules>
NDS DTD63
Allowed Content
ElementDescription
create-ruleObject creation rule. Deprecated as of Identity
Manager 2.0.
Attributes
None
Content Rule
( create-rule ) *
Parent Elements
novdocx (en) 13 May 2009
None
64Identity Manager 3.6 DTD Reference
delete
Used as an event notification from the PublicationShim to Identity Manager when an object is
deleted in the application. When used as a notification, an <association> is required. Also used as a
command from Identity Manager to the SubsciptionShim to delete an object in the application.
When used as a command, an <association> is required and is the unique key of the object to delete.
Remarks
A response to <delete> should be a <status> indicating whether or not the <delete> was processed
successfully.
The class name is mapped
between the application and
eDirectory namespaces by the
Schema Mapping policy so that
Identity Manager sees the name
in the eDirectory namespace and
a driver sees the name in the
application namespace.
#IMPLIED
dest-dn CDATA
The distinguished name of the
target object in the namespace of
the receiver.
Should be left empty for event
notifications.
#IMPLIED
NDS DTD65
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
dest-entry-id CDATA
The entry ID of the target object
in the namespace of the receiver.
Should be left empty for event
notifications.
event-id CDATA
An identifier used to tag the
results of an event or command.
qualified-src-dn CDATA
The qualified version of src-dn.
Only used for describing objects
from eDirectory.
src-dn CDATA
The distinguished name of source
object that generated the event in
the namespace of the sender.
src-entry-id CDATA
The entry ID of the source object
that generated the event in the
namespace of the sender.
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
Reserved. Should be ignored by
the driver.
timestamp CDATA
Reserved. Should be ignored by
the driver.
#IMPLIED
Content Rule
( association ? , operation-data ? )
Parent Elements
ElementDescription
inputInput events or commands.
66Identity Manager 3.6 DTD Reference
driver-config
Used to specify driver-specific configuration options. It is the top-level element in the XML stored
in the DirXML-ShimConfigInfo attribute of the DirXML-Driver object in eDirectory.
Remarks
The enclosed <driver-options>, <subscriber-options>, and <publisher-options> can each contain
any number of <config-object> and driver-defined elements. The driver-defined elements might
each contain text data.
Each driver-defined element can have a type attribute. The type attribute can specify that the
element refers to a named password by assigning the value password-ref to the attribute. A named
password reference is replaced at runtime with the actual value of a named password set using the
Identity Manager administration facilities.
In the Identity Manager administration interface, each driver defined element is displayed as an edit
control that can edit the content of the element. Each <config-object> is displayed as a single valued
dn control that allows the selection of a dn to fill in the dest-dn of enclosed <query>. Each control is
labeled with the value of the display-name attribute if it exists or with the tag name if it does not
exist.
Used to specify the event filter that is being used by a particular channel. It is generated from the
DirXML-DriverFilter attribute on the DirXML-Subscriber or DirXML-Publisher object.
Example
See <init-params>.
Allowed Content
ElementDescription
allow-classAllows a class in the filter.
Attributes
novdocx (en) 13 May 2009
AttributePossible ValuesDefault Value
type publisher | subscriber
Specifies the channel that the
filter is for.
#IMPLIED
Content Rule
( allow-class ) *
Parent Elements
ElementDescription
init-paramsInitialization parameters for a DriverShim,
SubscriptionShim, or PublicationShim.
NDS DTD69
driver-options
Used to specify driver-specific configuration options. It comes from the DirXML-ShimConfigInfo
attribute of the DirXML-Driver object in eDirectory.
Example
See <driver-config>.
Allowed Content
ANY
Attributes
None
novdocx (en) 13 May 2009
Content Rule
ANY
Parent Elements
ElementDescription
driver-configDriver specific DriverShim configuration options.
init-paramsInitialization parameters for a DriverShim,
SubscriptionShim, or PublicationShim.
70Identity Manager 3.6 DTD Reference
driver-state
Used specify driver specific state information.
Example
See <init-params>.
Allowed Content
ANY
Attributes
None
Content Rule
novdocx (en) 13 May 2009
ANY
Parent Elements
ElementDescription
init-paramsInitialization parameters for a DriverShim,
SubscriptionShim, or PublicationShim.
NDS DTD71
get-named-password
Used to retrieve a named password for a driver. A <status> result is returned indicating success or
failure. If the status is success, then a <password> element is also returned containing the password
value. The content of <get-namedpassword> is the name or key of the password that is retrieved.
An identifier used to tag the
results of an event or command.
#IMPLIED
Content Rule
( #PCDATA | operation-data ) *
Parent Elements
ElementDescription
inputInput events or commands.
72Identity Manager 3.6 DTD Reference
init-params
Used to specify initialization parameters for a DriverShim, SubscriptionShim, or PublicationShim.
Remarks
<init-params> is also included in any <output> or <input> from the driver to Identity Manager,
which instructs Identity Manager to store the contents of the enclosed <driver-state>, <subscriber-
state>, and <publisher-state> into the DirXML-DriverStorage attribute of the DirXML-Driver object
in eDirectory. The states are included in the <init-params> sent to the corresponding init() function
when a driver, subscriber, or publisher is started.
Used to encapsulate events or commands sent as input to a driver or Identity Manager. All <nds>
documents sent as a parameter to Identity Manager or driver interface method should contain
exactly one <input>.
Example
See <nds>.
Allowed Content
ElementDescription
addAdds an object when an add event occurs.
modifyModifies an object when a modify event occurs.
novdocx (en) 13 May 2009
deleteDeletes an object when a delete event occurs.
renameRenames an object when a rename event occurs.
moveMoves an object when a move event occurs
queryQuery command.
query-ex Query command with a result count limit.
query-schemaQuery schema command.
add-associationAdds association command.
modify-associationModifies an association command.
remove-associationRemoves an association command.
init-paramsInitialization parameters for a DriverShim,
SubscriptionShim, or PublicationShim.
statusStatus of the processing of a command or event.
check-passwordChecks password against an eDirectory driver
object.
modify-passwordModifies an object password when a modify event
for a password occurs.
check-object-passwordChecks password against an eDirectory object.
syncResynchronization or migrate event.
get-named-passwordRetrieves a named password for a driver.
Used to represent an object in eDirectory or the application as part of the response to a <query>
command or a <query-ex> command. <instance> does not necessarily represent the complete state
of object, but just the information requested by the <query> or <query-ex>. When returned from a
driver, an <association> is required.
The class name is mapped
between the application and
eDirectory namespaces by the
Schema Mapping policy so that
Identity Manager sees the name
in the eDirectory namespace and
a driver sees the name in the
application namespace.
event-id CDATA
An identifier used to tag the
results of an event or command.
qualified-src-dn CDATA
The qualified version of src-dn.
Only used for describing objects
from eDirectory.
src-dn CDATA
The distinguished name of the
source object that generated the
event in the namespace of the
sender.
#REQUIRED
#IMPLIED
#IMPLIED
#IMPLIED
src-entry-id CDATA
The entry ID of the source object
that generated the event in the
namespace of the sender.
Deprecated as of Identity Manager 2.0. Use DirXMLScript <if-op-attr> for an object creation and
Placement policy or <do-find-matching-object> and <arg-match-attr> for an object Matching policy.
Remarks
<match-attr> is used to specify:
Rule selection criteria for the enclosing <create-rule> or <placement-rule>. When used as such,
it must contain at least one <value>.
Object selection criteria for the enclosing <matching-rule>. When used as such, it must not
contain a <value>.
Example
See <create-rules>.
novdocx (en) 13 May 2009
Allowed Content
ElementDescription
valueThe attribute value.
Attributes
AttributePossible ValuesDefault Value
attr-name CDATA
The name of the required
attribute in the eDirectory
namespace.
#REQUIRED
Content Rule
( value ) *
Parent Elements
ElementDescription
create-ruleObject creation rule. Deprecated as of Identity
Manager 2.0.
matching-ruleObject matching rule. Deprecated as of Identity
Manager 2.0.
NDS DTD81
ElementDescription
placement-ruleObject placement rule. Deprecated as of Identity
Manager 2.0.
novdocx (en) 13 May 2009
82Identity Manager 3.6 DTD Reference
match-class
Deprecated as of Identity Manager 2.0. Use DirXMLScript <if-object-class> instead.
Remarks
<match-class> is used to specify rule selection criteria for the enclosing <matching-rule> or
<placement-rule>.
Example
See <matching-rules> and <placement-rules>.
Allowed Content
EMPTY
novdocx (en) 13 May 2009
Attributes
AttributePossible ValuesDefault Value
class-name CDATA
The name of the base class in the
eDirectory namespace.
#REQUIRED
Content Declaration
Empty
Parent Elements
ElementDescription
matching-ruleObject matching rule. Deprecated as of Identity
Manager 2.0.
placement-ruleObject matching rule. Deprecated as of Identity
Manager 2.0.
NDS DTD83
match-path
Deprecated as of Identity Manager 2.0. Use DirXMLScript <if-src-dn> for object placement policy
or <do-find-matching-object> and <arg-dn> for object matching policy.
Remarks
<match-path> is used to specify:
Rule selection criteria for the enclosing <placement-rule>. When used as such, the src-dn
attribute of the source <add> event is compared with prefix and is considered a match if the srcdn is in the subtree whose root is prefix. The namespace of the path is the same as the event
source.
Object selection criteria for the enclosing <matching-rule>. When used as such, prefix is used
as the dest-dn for the <query> generated by the enclosing rule. The namespace of the path is the
same as the event destination.
When the namespace of the path is eDirectory, the format is slash format, for example,
\treename\container\...\leaf. If the leading \ is omitted, the path is assumed to be relative to the tree
root.
novdocx (en) 13 May 2009
When the namespace of the path is the application namespace, the format of the path is application
dependent and should be documented by the driver writer.
Example
See <matching-rules> and <placement-rules>.
Allowed Content
EMPTY
Attributes
AttributePossible ValuesDefault Value
prefix CDATA
The root-most portion of the path
or distinguished name to match.
#REQUIRED
Content Declaration
EMPTY
84Identity Manager 3.6 DTD Reference
Parent Elements
ElementDescription
matching-ruleObject matching rule. Deprecated as of Identity
Manager 2.0.
placement-ruleObject matching rule. Deprecated as of Identity
Manager 2.0.
novdocx (en) 13 May 2009
NDS DTD85
matching-rule
Deprecated as of Identity Manager 2.0. Use DirXMLScript <rule> and <do-find-matching-object>
instead.
Remarks
<matching-rule> is used to specify the criteria for finding a matching object for automatic
association of a new object as a result of an <add> event.
When a <matching-rule> is evaluated, it first checks whether or not this is a suitable rule for the
<add> event in question. It does this by checking if any <match-class> elements are specified by the
rule. If so then the rule is only suitable if the class name on the event matches the class name on one
of the <match-class> elements. It then checks if any <modify-attr> criteria are specified by the rule.
If so, the rule is only suitable if the <add> contains an attribute value for each attribute specified by
a <match-attr>. If a rule is determined to not be suitable, it is skipped.
When a suitable rule is found, a <query> is generated based on the criteria specified by the rule
(<match-attr and <match-path>), and the class name and attribute values specified by the <add>.
This query is sent to the destination (eDirectory or driver). Any <instance> elements returned are
considered matches.
novdocx (en) 13 May 2009
Example
See <matching-rules>.
Allowed Content
ElementDescription
match-classMatches a class name. Deprecated as of Identity
Manager 2.0.
match-pathMatches a path. Deprecated as of Identity
Manager 2.0.
match-attrMatches an attribute. Deprecated as of Identity
Manager 2.0.
Attributes
AttributePossible ValuesDefault Value
description CDATA
#IMPLIED
86Identity Manager 3.6 DTD Reference
Description of this rule, primarily
for use in ConsoleOne.
Content Rule
( match-class * , match-path ? , match-attr * )
Parent Elements
ElementDescription
matching-rulesTop-level element for object matching rules.
Deprecated as of Identity Manager 2.0.
novdocx (en) 13 May 2009
NDS DTD87
matching-rules
Deprecated as of Identity Manager 2.0 - use DirXMLScript <policy>.
Remarks
<matching-rules> is the top level (document) element for object matching rules. Object matching
rules are stored in the DirXML-XmlData attribute of a DirXML-Rule object that is pointed to by the
DirXML-MatchingRule attribute of a DirXML-Subscriber or DirXML-Publisher object.
In the Subscriber channel, the source is eDirectory, and the destination is the application. In the
Publisher channel the source is the application and the destination is eDirectory.
Object matching rules are used to try to find a matching object in the destination for an unassociated
object in the source as a result of an <add> event in the source. (Note that DirXML automatically
converts <modify> into <add> for events from unassociated objects). Object matching rules are
applied before deciding if a new object should be created in the destination.
<matching-rules> contains 0 or more <matching-rule> elements. The matching rule processor
evaluates each <matching-rule> in order until one or more matching objects in the destination are
found.
novdocx (en) 13 May 2009
If exactly one matching object is found, that object is automatically associated with the source
object and Identity Manager attempts to reconcile any differences in the attribute values of the two
objects as allowed by the Publisher and Subscriber filters.
If more than one matching object is found, an error is signaled and the object either has to be
manually associated or the object matching rules has to be modified to be more specific.
If no matching objects are found, Identity Manager continues processing the event.
Example
<matching-rules>
<!-- for Users, first try to match on Surname, Given Name and
Location -->
<matching-rule>
<match-class class-name="User"/>
<match-attr attr-name="Surname"/>
<match-attr attr-name="Given Name"/>
<match-attr attr-name="Location"/>
</matching-rule>
<!-- for Users, then try to match on Surname only in -->
<!-- the o=novell subtree -->
<matching-rule>
<match-class class-name="User"/>
<match-path prefix="o=novell"/>
<match-attr attr-name="Surname"/>
</matching-rule>
<!-- for all classes try to match on CN only -->
<matching-rule>
<match-attr attr-name="CN"/>
</matching-rule>
</matching-rules>
88Identity Manager 3.6 DTD Reference
Allowed Content
ElementDescription
matching-ruleObject matching rule. Deprecated as of Identity
Manager 2.0.
Attributes
None
Content Rule
( matching-rule * )
Parent Elements
novdocx (en) 13 May 2009
None
NDS DTD89
modify
Used as an event notification from the PublicationShim to Identity Manager that an object is
modified in the application. When it is used as a notification, an <association> is required. It is also
used as a command from Identity Manager to the SubsciptionShim to modify an object in the
application. When it is used as a command, an <association> is required and is the unique key of the
object to modify.
Remarks
<add> contains a <modify-attr> for each attribute modified.
A response to <modify> should be a <status> indicating whether or not the <modify> is processed
successfully.
The class name is mapped
between the application and
eDirectory namespaces by the
Schema Mapping policy so that
Identity Manager sees the name
in the eDirectory namespace and
a driver sees the name in the
application namespace.
Required when used as a
notification.
dest-dn CDATA
The distinguished name of the
target object in the namespace of
the receiver.
Reserved. Should be ignored by
the driver.
dest-entry-id CDATA
The entry ID of the target object
in the namespace of the receiver.
#IMPLIED
#IMPLIED
#IMPLIED
Reserved. Should be ignored by
the driver.
event-id CDATA
An identifier used to tag the
results of an event or command.
from-mergetrue | false
True if the command is the result
of a merge
qualified-src-dn CDATA
The qualified version of src-dn.
Only used for describing objects
from eDirectory.
src-dn CDATA
The distinguished name of the
source object that generated the
event in the namespace of the
sender.
#IMPLIED
false
#IMPLIED
#IMPLIED
NDS DTD91
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
src-entry-id CDATA
The entry id of the source object
that generated the event in the
namespace of the sender.
Reserved. Should be ignored by
the driver.
timestamp CDATA
Reserved. Should be ignored by
the driver.
#IMPLIED
#IMPLIED
Content Rule
( association ? , modify-attr + , operation-data ? )
Parent Elements
ElementDescription
inputInput events or commands.
92Identity Manager 3.6 DTD Reference
modify-association
Used to notify Identity Manager that an application object's unique key is modified. <modifyassociation> should be sent when the unique key is changed for an object that passes the event filter
for either the SubscriptionShim or the PublicationShim. <modify-association> can be included in
any <output> or <input> from the driver to Identity Manager.
An identifier used to tag the
results of an event or command.
#IMPLIED
Content Rule
( association , association , operation-data ? )
Parent Elements
ElementDescription
inputInput events or commands.
outputResults of events or commands.
NDS DTD93
modify-attr
Used to specify the modified attribute values for a <modify> operation or event.
Remarks
Each <modify-attr> should contain at least one <add-value>, <remove-value>, or <remove-all-
values>.
The order of the above elements is significant.
Example
See <modify>.
Allowed Content
novdocx (en) 13 May 2009
ElementDescription
remove-valueRemoves the specified attribute values.
remove-all-valuesRemoves all attribute values.
add-valueAdds values.
Attributes
AttributePossible ValuesDefault Value
attr-name CDATA
The name of the attribute.
The name is mapped between
the application and eDirectory
namespaces by the Schema
Mapping policy so that Identity
Manager sees the name in the
eDirectory namespace and a
driver sees the name in the
application namespace. The
Mapping policy uses the class
name attribute of the enclosing
command or event to determine
which class to use for mapping
the attribute name.
modifyModifies an object when a modify event occurs.
novdocx (en) 13 May 2009
NDS DTD95
modify-password
Used as an event notification from the PublicationShim to Identity Manager that an object password
is modified in the application. When used as a notification, an <association> is required. Also used
as a command from Identity Manager to the SubsciptionShim to modify an object password in the
application. When used as a command, an <association> is required and is the unique key of the
object to modify.
Remarks
When the target is eDirectory, and <old-password> is specified, the modifyPassword API is used to
modify the password. If not specified, the GenerateKeyPair API is used. Using GenerateKeyPair
might invalidate authentication credentials for any existing session authenticated as the target object.
When the target is the application, a driver might or might not implement this functionality,
depending on the applicability to the application.
A response to <modify-password> should be a <status> indicating whether or not the <modifypassword> is processed successfully.
The class name is mapped
between the application and
eDirectory namespaces by the
Schema Mapping policy so that
Identity Manager sees the name
in the eDirectory namespace and
a driver sees the name in the
application namespace.
Required when used as a
notification.
dest-dn CDATA
The distinguished name of the
target object in the namespace of
the receiver.
dest-entry-id CDATA
The entry ID of the target object
in the namespace of the receiver.
Reserved. Should be ignored by
the driver.
#IMPLIED
#IMPLIED
#IMPLIED
event-id CDATA
An identifier used to tag the
results of an event or command.
qualified-src-dn CDATA
The qualified version of the srcdn. Only used for describing
objects from eDirectory.
src-dn CDATA
The distinguished name of the
source object that generated the
event in the namespace of the
sender.
src-entry-id CDATA
The entry ID of the source object
that generated the event in the
namespace of the sender.
Used as an event notification from the PublicationShim to Identity Manager when an object is
moved to a different container in the application. When used as a notification, an <association> is
required. Also used as a command from Identity Manager to the SubsciptionShim to move an object
to a different container in the application. When used as a command, an <association> is required
and is the unique key of the object to move.
Remarks
<move> contains a <parent> that specifies the new container. When used as a command, the
<parent> can contain an <association>. If it does not contain an association, the driver should not
attempt to move the object and should return a <status> level=“warning”.
A response to <move> should be a <status> indicating whether or not the <move> is processed
successfully.
operation-dataThe operation adds additional custom data
NDS DTD99
Attributes
AttributePossible ValuesDefault Value
novdocx (en) 13 May 2009
class-name CDATA
The name of the base class of the
object.
The class name is mapped
between the application and
eDirectory namespaces by the
Schema Mapping policy so that
Identity Manager sees the name
in the eDirectory namespace and
a driver sees the name in the
application namespace.
dest-dn CDATA
The distinguished name of the
target object in the namespace of
the receiver.
Reserved. Should be ignored by
the driver.
dest-entry-id CDATA
The entry ID of the target object
in the namespace of the receiver.
Reserved. Should be ignored by
the driver.
#IMPLIED
#IMPLIED
#IMPLIED
event-id CDATA
An identifier used to tag the
results of an event or command.
old-src-dn CDATA
The original distinguished name
of the source object that
generated the event in the
namespace of the sender.
qualified-old-src-dn CDATA
The qualified version of the oldsrc-dn. Only used for describing
objects from eDirectory.
qualified-src-dn CDATA
The qualified version of the srcdn. Only used for describing
objects from eDirectory.
#IMPLIED
#IMPLIED
#IMPLIED
#IMPLIED
100 Identity Manager 3.6 DTD Reference
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.