Previous Topic: Passing Global User AttributesNext Topic: Example Files

Connector Guides › Connectors Guide › Connecting to Endpoints › Microsoft Active Directory Services Connector › Connector-Specific Features › Program Exits › Creating Custom ADS Attributes

Creating Custom ADS Attributes

The file PS_HOME\data\ADS\schema.ext is used to create custom ADS attributes.

Note: You must first create this file.

Custom ADS attributes are placed one per line in the text file PS_HOME\data\ADS\schema.ext. This file is used to specify any custom ADS account attributes that have been added to the ADS schema and any ADS account attributes that do not actually exist in the ADS schema but are used in ADSExitUsrPreAdd.txt and ADSExitUsrPostAdd.txt. For more information on extending the ADS schema, see the topic Extending the ADS Schema in the ADS Defaults section.

To let the ADS connector know that the custom ADS account attribute being added is to be used for exit processing and does not exist in ADS, the attribute name in schema.ext must begin with eTADSExitOnly. This prefix lets the ADS connector know that the custom attribute can be passed to the ADS connector command line interface. Since the attribute does not exist in the ADS schema, the syntax and the single or multi-value indicator must be included in the schema.ext. These two values follow the attribute name and are delimited with a colon (:). An example of a line in schema.ext follows:

eTADSExitOnlyDiskSize:2.2.5.12:T

The syntax of the attribute is 2.2.5.12. These syntaxes are defined at the following website:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/mapping_active_directory_syntax_to_adsi_syntax.asp

The following characters indicate the value of the attribute:

Note: Any changes to the schema.ext require a restart of the CA IdentityMinder Provisioning service and the Provisioning Manager.

By default, any attribute listed is assumed to exist for both contacts and accounts. To indicate that a given attribute is to be defined for accounts or contacts only, add an optional prefix (account) or (contact) to the attribute name. Optionally, you can use the prefix (both) to indicate an attribute is valid for both accounts and contacts.

For example, your installation added three new attributes to the schema. BirthDate is valid for accounts only. SSN is valid for accounts and contacts. DoNotCall is valid for contacts only. You can add these entries into your schema.ext file as follows: