The Attribute Details dialog lets you define logical parameters that control how a specific provisioning attribute is handled.
This dialog contains the following fields:
Defines the name of the attribute. This label appears in user interfaces to represent the attribute.
(Optional) Describes the attribute.
Specifies which name to map an object class (including the connector itself) or attribute to in connector-speak. For a dynamic connector, this attribute specifies the name of the native system item to map the attribute to. For example, a JDBC-based connector would probably map an object class to the name of a database table, and each property within it to the name of one of its columns.
(Optional) Specifies the default value for the attribute.
Note: Only clients use this value (for example, user interfaces). If the client does not supply a value, the Provisioning Server does not use it by default.
If selected, specifies that the endpoint requires that this attribute is present in all objects of this type.
Note: If the endpoint schema requires this attribute to be present, Connector Xpress automatically selects the check box, and you cannot clear the check box.
Specifies the minimum byte length of values for this attribute value.
This value is used for input validation in CA IdentityMinder account screens.
Specifies the maximum byte length of values for this attribute value.
This value is used for input validation.
Specifies the operations you can perform on this attribute. Select at least one of the following options:
Specifies whether the value of the attribute is set when creating an object instance of the parent class.
Specifies whether value of the attribute is read when viewing an object instance of the parent class.
Specifies whether value of the attribute is set when modifying an object instance of the parent class.
(Numeric attribute types) Specifies the minimum value you can set for this attribute.
(Numeric attribute types) Specifies the maximum value you can set for this attribute.
Specifies the data type of the provisioning attribute that you have mapped to the native attribute.
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
Specifies the case of the connector-speak value of a string.
Specifies that the case is set to uppercase.
Example: If set to upper, String is set to STRING
Specifies that the case is set to lowercase.
Example: If set to Lower, STRING is set to string.
Specifies that the case of the string is preserved.
Note: The endpoint might not enforce case-sensitive searching, so a search for "EXAMPLE" can still match "eXaMpLe" on the endpoint system.
If selected, specifies that this attribute is multi-valued.
JNDI: Selected only if the native attribute is multi-valued. Read-only if native attribute is single valued.
JDBC: Default is unselected.
(JDBC only) Specifies the flattening style you want to use.
Specifies that the multiple values of the attribute are comma-separated.
Specifies that the multiple values of this attribute are in SQL format.
Specifies that the multiple values of this attribute are in XML format.
Specifies whether Connector Xpress trims leading and trailing whitespace from the attribute's value.
Specifies whether user interfaces use asterisks to mask the attribute's value.
Overrides the default 0 and 1 symbolic values for false and true values for Boolean attribute types.
True
Specifies the symbolic value used for true.
Specifies the symbolic value used for false.
Sets the metadata value for isStoreSymbolic or isStoreNumeric.
Specifies that Boolean (and enum) values are written as their numeric counterparts.
Specifies that numeric text is expected in LDAP but that equivalent symbolic values are stored in connector-speak. That is, boolean and enum attributes are written as their symbolic value.
Specifies that Boolean (and enum) values are written as their numeric counterparts.That is, boolean and enum attributes are written as their numeric values.
Note: This option is only available for Boolean and (static) Enumerations data types. When both boolean values fields are set, this value changes to Symbolic, as setting boolValues has no effect.
Specifies how the default value for this attribute is generated used in the default account template.
Specifies that this attribute does not have a value in the default account template.
Specifies the value of this attribute used in the default account template.
Specifies that the value of this attribute used in the default account template is generated by a rule string.
Note: For more information about Rule Strings, see the CA IdentityMinder Administration Guide.
Specifies whether this attribute is updated when this account is synchronized with its templates.
Specifies that the attribute is stored by the Provisioning Server and can be retrieved without consulting the endpoint system.
For example, credentials used to connect to the endpoint system must be cached, otherwise the user might have to provide the credentials every time the connector is acquired. You may also need to cache a value because querying an endpoint system for the value can take a long time to compute.
Specifies whether this attribute is a well-known attribute.
Specifies the JavaBean Property name used for this attribute in the JIAM API. If you select a value in the Well-Known Name list, you cannot edit this value.
Specifies that this attribute's value may be too expensive to return in general searches. If selected, searches only return the attribute value if explicitly asked for.
This feature does not work. If you want to convert your data using regular expressions, create a new flexi string type for any attributes that you want to convert and add the conversion to the override connector XML file for the connector type.
Specifies the recommended character width of the user interface input field for this attribute. If not used, Connector Xpress uses the attributes data type and maximum length to define an appropriate input field length.
Specifies the generator expression used by the CA IAM CS.
To pass the value to the endpoint system literally, enclose the expression in double quotes.
Example: \"NEXT VALUE FOR my_sequence\"
If you do not enclose the expression in double quotes, the connector must know how to interpret the value. For example, JDBC knows the value provided is a sequence name.
Example: \'my_sequence\'
Specifies that that the value for property is generated implicitly by the endpoint. For example, true for IDENTITY columns in JDBC.
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.
|
|