The next step in this configuration is to map values from the token processor into the attributes required by the token generator (the Token Generator Contract).
Map each attribute to fulfill the Token Generator Contract from one of these Sources:
When you make this selection, the associated Value drop-down list is populated by the token processor.
Values are returned from the context of the transaction at runtime.Note:
The HTTP Request selection is retrieved as a Java object rather than text. For this reason, OGNL expressions are more appropriate to evaluate and return values.
Choose Expression and then click Edit to enter an expression (see Using the OGNL edit screen). (If the Expression selection is not listed, then the feature is not enabled—see Enabling and disabling expressions. For syntax and examples, see sections under Construct OGNL expressions.)
- LDAP/JDBC/Other (when a datastore is used)
Values are returned from your datastore (if used). When you make this selection, the Value list is populated by the attributes from the datastore.
- Expression (when enabled)
This option provides more complex mapping capabilities—for example, transforming incoming values into different formats (see Attribute mapping expressions). All of the variables available for text entries (see below) are also available for expressions.
- No Mapping
Select this option to ignore the Value field, causing no value selection to be necessary.
The value is what you enter. This can be text only, or you can mix text with references to any of the values from the token processor, using the
You can also enter values from your datastore, when applicable, using this syntax:
attr-source-idis the Attribute Source ID value (see Fulfillment by datastore queries) and
attributeis any of the datastore attributes you select.
- Select a source of the attribute under Source for each attribute in the contract of the token generator.
- Specify an attribute under Value for each attribute.