For JNDI, the Map Attributes dialog lets you specify the native object class attributes (JNDI) that you want to map a provisioning attribute to.
For JDBC, the Map Attributes dialog lets you specify the table column names that you want to map a provisioning attribute to.
You can map any attributes of the selected structural and auxiliary classes defined in the class mapping.
Any provisioning attribute that is mapped to multiple endpoint attributes will have a choice attribute generated for it. For ease of use, these should be placed on your user console account screens near the attribute in question.
For the Account class, the attribute mapping table is pre-populated with the recommended common account attribute set for ease of use. You do not have to map all of these attributes.
This dialog contains the following fields:
Displays the provisioning display name of the attribute.
The naming attribute of the class in question is displayed in bold.
Specifies the data type of the provisioning attribute that you have mapped to the native attribute.
Default: String. You can change the default if necessary.
Important! The data model type is important because it drives data validation and conversion in clients and the CA IAM CS. The following types match syntax that is defined as part of the XML schema (XSD) specification. You can find information about the XML schema definition at the following website:
Defines an attribute whose value is arbitrary binary data.
Specifies logically true or false in XML, but represented by the Provisioning Server and JIAM APIs as 1 or 0 in LDAP attribute values.
Specifies a date.
Example: 1999-05-31
Note: The Dynamic Namespace plug-in to Provisioning Manager supports the years from 1800 through 9999. Other components of the solution impose no such restrictions and can represent virtually any year in recorded history.
Specifies a particular time on a particular day.
Example: 1999-05-31T13:20:00
Note: The Dynamic Namespace plug-in to Provisioning Manager supports the years from 1970 through 2036, so you must use Date to represent days falling outside of this range.
Note: Vendor differences complicate how Connector Xpress handles time-related columns. For example, MSSQL “DATETIME” signifies a DateTime value whereas other vendors use the standard “TIMESTAMP”, and MSSQL TIMESTAMPs are automatically generated binary values. Also, Oracle does not support a “TIME” type and its “DATE” type is also effectively a TIMESTAMP. Therefore, to remain vendor-neutral, Connector Xpress allows you to map to any of Date/DateTime/Time whenever it makes sense for you to do so.
Specifies a double-precision 64-bit floating-point value.
Specifies an attribute with a fixed list of enumerated values.
Specifies a distinguished name string format.
For example, "cn=Bob,ou=Sales,o=ExampleCorp". The connector enforces this.
Specifies an email address string format.
Specifies that quotes are removed from attribute values.
Specifies a single-precision 32-bit floating-point number.
Specifies a 32-bit value between -2147483648 and 2147483647.
Specifies a 64-bit value from 9223372036854775808 through 9223372036854775807.
Specifies an unrestricted field.
Specifies an offset of between 0 seconds and 23:59:59.
Example: 13:20:00
If selected, specifies that this attribute is multi-valued.
Note: If the native attribute is multi-valued, Connector Xpress automatically selects this check box. If the native attribute is single-valued, this option is cleared and read-only.
Displays the native attribute names that the provisioning attribute is mapped to.
Displays an extended set of metadata properties. These fields are displayed when you select the Show extended set of metadata properties on the Connector Xpress Preferences dialog.
Note: For more information, see Extended Metadata Properties.
|
Copyright © 2013 CA.
All rights reserved.
|
|