Close the page or edit as described in Step 4. Proceed to Step 4, if needed, or to

Writing Oracle Security Token Service Module Classes 4-15 ■ Figure 4–8, Token Mapping: email-wstrust-valid-temp Figure 4–7 General Details: email-wstrust-valid-temp Figure 4–8 Token Mapping: email-wstrust-valid-temp To create the validation template for the custom module classes 1. Display the list of existing Token Validation Templates. Oracle Access Suite System Configuration Security Token Services Token Validation Templates

2. Click the New Validation Template button in the upper-right corner or click the

Add + command button above the Search Results table.

3. General: Set the following for use with the custom token.

See Also: Oracle Fusion Middleware Administrators Guide for Oracle Access Manager with Oracle Security Token Service 4-16 Developers Guide for Oracle Access Manager and Oracle Security Token Service Validation Template Name: email-wstrust-valid-temp Token Protocol: Webservice Trust Token Type: email Default Partner Profile: requester-profile Custom Validation Attributes: testsetting: hello 4. Token Mapping: Set the following for use with the custom token in this chapter. Check the box beside Map Token To User to enable it. Check the box beside Enable Simple User Mapping and enter: User Token Attribute: STS_SUBJECT_ID Datastore Attribute: mail 5. Click Save and dismiss the confirmation window. 6. Proceed to Creating the Issuance Template for a Custom Token .

4.5.2 Creating the Issuance Template for a Custom Token

This is a server side configuration. Users with valid Oracle Access Manager administrator credentials can perform the following task to create a Token Issuance Template. Each Token Issuance Template indicates how to construct a token, and which signing or encryption to use when constructing a token. Each Token Issuance Template also defines the attributes to be sent as part of the outbound token for mapping, and filtering data. However, Issuance Templates do not list mapping or filtering rules, which are defined in the Relying Party Partner Profile. The template in this example can be used for the email custom token described earlier in this chapter. Implementation details are shown in the following figures, and described in the accompanying procedure. As you review these, notice how specifications for this template reference the module class code: ■ Figure 4–9, General Details: email-issuance-temp ■ Figure 4–10, Issuance Properties: email-issuance-temp Figure 4–9 General Details: email-issuance-temp