38 Managing Templates, Endpoints, and Policies

38.2.1 About Template Search Controls

The following figures show the search pages where you will see many similarities:

• Figure 38-1, "Validation Templates Search Controls"

• Figure 38-2, "Issuance Template Search Controls"

Figure 38-1 Validation Templates Search Controls

Description of "Figure 38-1 Validation Templates Search Controls"

Figure 38-2 Issuance Template Search Controls

Description of "Figure 38-2 Issuance Template Search Controls"

Table 38-1 describes the controls available to refine a template search. Unless explicitly stated, all elements are available for both Validation and Issuance Template searches.

Table 38-1 Search Validation Template

Element	Description
Match	Choose All to search for a template that matches all your specifications. Choose Any to search for a template that matches at least one of your specifications.
Search Operations List	A list of operations from which you choose one to help refine your search.
... Template Name	Choose an operation from the list and enter information in the field to help refine your search.
Description	Refine your search using the optional description field.
Token Protocol Validation Template only	Choose the token protocol from those listed: WS-Trust WS-Security
Token type	Choose the token type. Both standard and custom token types are included. Username: Consumption and Creation X.509: Consumption SAML: Consumption & Creation OAM 11g: Consumption using the OBO (on behalf of) field Kerberos: Consumption Custom: Consumption the OBO (on behalf of) field and Creation
Search	Initiates the Search function using criteria in the form.
Reset	Resets the Search form with defaults only.
Add Fields	A list of additional items you can add as search criteria.
Search Results Table	Itemizes the results of your search based on choices in the View menu, described later in this table.
Actions menu Shown: Actions for Validation Template	Provides the following functions that can be performed on a selection in the results table: Note: Actions menu functions mirror command buttons above the results table. For example: New ... Template: Click the New ... Template button at the top of the Search page, or select New ... Template from the menu, or click the + button above the table. Edit: Click a name in the Results Table, or select Edit from the Actions menu, or click the Edit (pencil) command button above the Results Table. Create Like: Select the desired row in the table and either select Create Like from the Actions menu, or click the Create Like command button above the table Remove: Select the desired row in the Results Table and either select Delete from the Actions menu, or click the Delete (X) command button above the table.
View menu Validation Template only	A list from which you can identify which information to display in the results table.
View menu Issuance Template only	A list from which you can identify which information to display in the results table.
	Controls you can choose to define the order of items listed in the results table: Ascending Descending

38.2.2 Searching For a Template

Users with valid Administrator credentials can use the following procedure to use search controls to locate a specific template or set of templates. For example, to locate all templates of a certain token type you can simply choose the type of token. To refine the search further to all templates of a specific token type and name.

When performing these steps, fill in as much or as little as you want. Skip any steps that do not apply to you.

To search for a template

1. From the Oracle Access Management Console, click Token Validation Templates.

2. Edit Search Criteria (Table 38-1). For example:

   • Match: All

   • Name: contains em

   • Token Type: equals Username

3. Click Search, review results, and click the one you want to open.

38.3.1 About Managing Token Issuance Templates

Each Token Issuance Template indicates how to construct a token. In other words, which signing or encryption to use when constructing a token. Each Token Issuance Template also defines the attributes mapping and filtering rules to be applied to the attributes that will be included in the outgoing token. However, Issuance Templates do not list the attributes that will be sent in the outgoing token: these are defined in the Relying Party Partner Profile.

Token Issuance Template details which will differ depending on your chosen token type. Table 38-2 describes where to find more information.

General Details

Figure 38-3 shows the New Issuance Template page with defaults showing. Unless explicitly stated, General information is the same regardless of the Token Type you choose. For more information, see Table 38-3. After you fill in General information and click Save, you cannot return and edit the template name or token type.

Figure 38-3 Issuance Template: General Details and Defaults

Description of "Figure 38-3 Issuance Template: General Details and Defaults"

Issuance Properties: Username Token Type

If the token type is Username, the Issuance Properties shown in Figure 38-4 are needed for a Username token type template.

Figure 38-4 Issuance Properties: Username Token Type

Description of "Figure 38-4 Issuance Properties: Username Token Type"

Table 38-4 describes the Issuance Properties for the Username token type.

Issuance Properties: SAML Token Types

SAML 1.1 and 2.0 token types require the issuance properties illustrated in Figure 38-5.

Figure 38-5 Issuance Properties: SAML Token Types

Description of "Figure 38-5 Issuance Properties: SAML Token Types"

Table 38-5 describes all Issuance Properties by token type. Only SAML token types require issuance properties.

Table 38-5 Issuance Properties: SAML Token Types

Element	Description
Assertion Issuer	Specifies the identifier representing the issuer of the assertion. This string is used to represent this Security Token Service as the issuer of the assertion.
Name Identifier Format	Choose a format from the list and then enter the details in the text field.
Name Identifier Qualifier	Contains the string that will be set as the Name Identifier Qualifier.
Name Identifier User Attribute	References the attribute that will be used to populate the value of the Name Identifier.
Name Identifier User Attribute Store	Userstore Context Note: If the Attribute Store is the Userstore, LDAP is used to retrieve the attribute from the user record. If the Attribute Store is context, data from the incoming token is used as the attribute source.
Include Authentication Statement	Indicates whether or not a SAML Authentication Statement should be included in the Assertion. Default: Disabled Note: An authentication operation is required for a statement of this type to be included. An authentication statement will be included if the incoming token contained some authentication data and that those were validated (for example, the incoming SAML Assertion contains an authentication statement, or a Username Token contains credentials that were validated).
Include Attribute Statement	Indicates whether or not a SAML Attribute Statement will be included in the outgoing Assertion. A statement of this type will be included only if this flag is set to true and if at least one attribute is included in the outgoing Assertion. Default: Enabled Note: the RP PP will determine which attributes need to be included in an outgoing token.
Validity Period	Specify the length of time (in seconds) that the token will be valid. Default: 3600 (seconds)

Security Details: SAML Tokens

Only SAML token types require Security Details, as shown in Figure 38-6 and described in Table 38-6.

Figure 38-6 Security Details: SAML Tokens

Description of "Figure 38-6 Security Details: SAML Tokens"

Table 38-6 Security Details: SAML Tokens

Elements	Description
Signing And Encryption	Indicates whether or not the Assertion will be signed using the Key referenced by the Signing Keystore Access Template ID field.
Sign Assertion	Indicates whether or not the signing certificate will be included in the Assertion. Default: Enabled
Include Certificate in Signature	Default: Enabled
Signing Keystore Access Template Id	References the key to be used to sign assertions created with this issuance template. The key templates are defined in the Security Token Service Settings section.
Subject Confirmation
Default Subject Confirmation Method	Indicates which Subject Confirmation Method will be used by default, if the requester did not specify a method in the WS-Trust request. Possible values are: Bearer Holder of Key with Public Key Holder of Key with Symmetric Key Sender Vouches
Compute Holder-of-Key Symmetric Key	Default: Enabled Indicates whether or not Security Token Service will generate random data when creating the Secret Key for the Holder of Key Symmetric Key data. If true, the server will generate the secret key if the client did not specify entropy. Otherwise it will derive the key from the client and server entropy If false, the client entropy will be used as the secret key
Encrypt RSTR Proof Token	Indicates whether or not the Proof Token must be encrypted when returning the server entropy or secret key to the requester in the WS-Trust response, when the Subject Confirmation method is Holder of Key with Symmetric Key Default: Disabled
Holder-of-Key Symmetric Key Generation Algorithm	Indicates the symmetric key generation algorithm to use to create the secret key when the Subject Confirmation method is Holder of Key with Symmetric Key:

Attribute Mapping: SAML Tokens

When the token type is SAML 1.1 or 2.0, it is possible to define attribute mapping and filter rules that will be applied to the attributes included in the Assertion.

There are three different rules:

• Attribute name mapping where the local name of an attribute can be changed to another value. For example, givenname can be changed to firstname.

• Attribute value mapping where the local value of an attribute can be translated to another value. For example, President to CEO.

• Attribute value filtering where the local value of an attribute can be filtered so it is not included in the outgoing assertion. For example, some sensitive attribute values could be removed while others would be issued.

Attribute Value Condition Filters

This optional value filtering applies to an Attribute Name mapping and will be included in the Assertion. To define an attribute filtering for an attribute, you must first define an attribute name mapping for that attribute. The Condition is associated with the expression to determine whether or not the attribute value should be filtered. The possible Condition values are:

• regexp: the expression will contain a regular expression, and if it evaluates to true, the attribute value will be filtered.

• equals: if the attribute value matches the data contained in the expression field, then it will be filtered.

• not-equals: if the attribute value does not match the data contained in the expression field, then it will be filtered.

• not-equals: if the attribute value does not match the data contained in the expression field, then it will be filtered.

• endswith: if the attribute value ends with the data contained in the expression field, then it will be filtered.

• contains: if the attribute value contains an occurrence of the data contained in the expression field, then it will be filtered.

• not-contains: if the attribute value does not contains any occurrence of the data contained in the expression field, then it will be filtered.

• equals-null: if the attribute value is null, then it will be filtered.

• not-equals-null: if the attribute value is not null, then it will be filtered.

38.3.2 Managing a Token Issuance Template

Users with valid Oracle Access Management Administrator credentials can use this procedure as a guide when developing a new Token Issuance Template (or editing an existing template) Skip any steps that do not apply to you.

The following procedure describes how to create a new Token Issuance Template for a Security Assertion Markup Language (SAML) token.

Prerequisites

Confirm that the desired LDAP Identity Store is registered with and configured as the Default Store.

To create a new token Issuance template

1. Display the list of existing Token Issuance Templates.

   
   Oracle Access Management Console Launch Pad
   Security Token Service
   Token Issuance Templates
   

2. New Token Issuance Template:

   1. Click the New Issuance Template button in the upper-right corner (or click the Add (+) command button above the Search Results table).

   2. General: Define general information for this template and see:

      Table 38-3, "Issuance Template: General Details"

   3. Click Save and dismiss the confirmation window (or click Cancel without saving).

   4. Username Token Type: Define issuance parameters for this template and see:

      Table 38-4, "Issuance Properties: Username Token Type"

   5. SAML Token Type: Define parameters for this template and see:

      Table 38-5, "Issuance Properties: SAML Token Types"

      Table 38-6, "Security Details: SAML Tokens"

      Table 38-7, "Issuance Template: Attribute Mapping, SAML Token"

   6. Click Apply (or click Revert without saving it).

   7. Close the definition.

3. Find an Existing Template: From the Security Token Service section of the Oracle Access Management Launch Pad:

   1. Find All: Double-click the Token Issuance Templates node and review the results table.

   2. Narrow the Search: Specify your search criteria (Table 38-1), click the Search Button, and review the results table.

   3. Reset the Search Form: Click the Reset button.

4. Edit a Template: Start with the saved page you just created.

   Alternatively: Use Step 3 to find the desired template and click the name in the Search Results table to display the definition.

   1. Edit details as needed.

   2. Click the Apply button at the top of the page to submit changes (or Revert to undo your changes).

5. Remove a Template:

   1. Click the desired name in the Search Results table to select the item to remove.

   2. From the Actions menu, click Delete (or click the Delete (X) command button above the table.

   3. Click the Delete button in the Confirmation window (or click No to cancel the operation).

38.4.1 About Managing Token Validation Templates

A Security Token Service Endpoint is always mapped with a WS-Security Validation Template that indicates how to map the request to a requester entry or to a user:

• If mapping is required and no match is found, processing will fail.

• If no mapping is required, a default requester partner profile will be used.

• In either case, a requester partner profile is retrieved.

• If a mapping is performed to a user record, a default requester partner profile will be used.

• If a mapping is performed to a requester partner entry, the requester partner profile for this partner will be used.

A validation template determines the token validation rules:

• Whether or not to validate and map the incoming token.

• The mapping rules to be used if mapping is enabled.

A validation template is specific to a token type and specific to a protocol as described in Table 38-8.

A validation template mapping rules determines how the incoming data is mapped to a user or a partner, using data from the incoming token:

• Username for Username Token

• UserID for Kerberos Token

• NameID and attributes for SAML Token

• DN Components for X.509 Token

• Attributes from a Custom

Mapping is performed as follows:

• Simple mapping: one incoming attribute matched against one user record attributes

• Complex LDAP query: LDAP query with placeholders for incoming data (e.g.: (&(sn=%lastname%)(mail=%email%))

• NameID Mapping table for SAML Token

Figure 38-7 illustrates default General details on the New Validation Template page.

Figure 38-7 New Validation Template page: General Page Defaults

Description of "Figure 38-7 New Validation Template page: General Page Defaults"

Table 38-9 describes the elements on the New Validation Template, General page.

Figure 38-8 illustrates the General details page when Enable Credential Validation is checked and, as a result, the Authentication Details section of the page is visible with its default values. This is specific to username token validation.

Figure 38-8 New Validation Template: General Authentication Details

Description of "Figure 38-8 New Validation Template: General Authentication Details"

Table 38-10 describes Authentication related details that are available when you choose Enable Credential Validation.

Token Mapping

The Token Mapping section indicates the following:

• If an incoming token needs to be mapped.

• If the incoming token needs to be mapped, what kind of mapping is done. For example, mapping token to user, mapping token to partner, and so on.

• How the mapping is done. For example, by mapping a token attribute to a partner/user attribute, or by using an LDAP query involving several token attributes.

Mapping rules determine how the incoming data is mapped to a user or a partner. The following data of the incoming token is used:

• Username for UNT

• UserID for Kerberos

• NameID and attributes for SAML

• DN Components for X.509

• Attributes from custom

Mapping is performed using the following:

• Simple mapping: One incoming attribute matched against one user record attributes.

• Complex LDAP query: An LDAP query with placeholders for incoming data. For example, (&(sn=%lastname%)(mail=%email%))

• A NameID Mapping table for SAML

Following are several Token Mapping Examples for a new Validation Template:

• Figure 38-9, "Token Mapping: SAML2 WS-Security Validation Template"

• Figure 38-10, "Token Mapping, username-wstrust-validation-template"

• Figure 38-11, "Token Mapping: x509-wss-validation-template"

Figure 38-9 shows the mapping configuration settings required for Security Token Service to map the token to a user record, by matching the NameID value to user records that have a matching attribute, based on the NameID format:

• Enable Map Token to User

• Enable Simple User Mapping

• Disable Attribute Based User Mapping

Figure 38-9 Token Mapping: SAML2 WS-Security Validation Template

Description of "Figure 38-9 Token Mapping: SAML2 WS-Security Validation Template"

Figure 38-10 shows the mapping configuration settings required for Security Token Service to map the token to a user record by matching the username element of the Username token to a user record that has a matching uid. The required settings are:

• Enable Map Token to User

• Enable Simple User Mapping

• Datastore Attribute set to uid

• Disable Attribute Based User Mapping

Figure 38-10 Token Mapping, username-wstrust-validation-template

Description of "Figure 38-10 Token Mapping, username-wstrust-validation-template"

Figure 38-11 shows the mapping configuration settings required for Security Token Service to map the token to a requester partner entry by matching the Subject DN of the certificate to a Requester Partner that has a match on SSL Client Cert DN Identification attribute. The required settings are:

• Map Token to Partner

• Disable Simple User Mapping

• Disable Attribute Based User Mapping

• Enable Simple Partner Mapping

Figure 38-11 Token Mapping: x509-wss-validation-template

Description of "Figure 38-11 Token Mapping: x509-wss-validation-template"

Not all elements apply to all token types and token protocols. The elements that you must define will vary.

Table 38-11 describes the token mapping elements for validation templates.

38.4.2 Managing Token Validation Templates

This is a server side configuration. A default Token Validation Template exists. Users with valid Administrator credentials can use can use the procedure in this section to add, find, edit, or delete token validation templates. Skip any steps that you do not need.

The Security Token Service Endpoint must be linked to a WS Security Validation Template that indicates:

• how to validate the token in the Webservice Security header

• how to map the token and binding data to a Requester

The information here can be applied when you want to validate the following:

• WS-Security tokens present in the SOAP Header, of type: Username, SAML 1.1, SAML 2.0, X.509 and Kerberos.

• WS-Trust tokens present in the OnBehalfOf element or in the ValidateTarget element of the WS-Trust request, of type: Username, SAML 1.1, SAML 2.0, X.509, Kerberos, OAM Session Propagation Token and custom tokens.

The following procedure includes several examples of input following specific parameters. Also, a brief translation appears within parentheses (). For instance: Name (username-token): email-wstrust-valid-temp. Values in your environment will be different.

Prerequisites

To manage token validation templates

1. Locate and open the desired Token Validation Template as described in "Searching For a Template".

2. New Token Validation Template:

   1. Click the New Validation Template button in the upper-right corner (or click the Add (+) command button above the Search Results table).

   2. General: Define parameters for this template (Table 38-9). For example:

      
      Name (username-token): email-wstrust-valid-temp
      Token Protocol (WS-Security for token protocol): Webservice
      Token Type (username): email
      Default Partner Profile: requester-profile
      

   3. Authentication: Enable Credential Validation for this template, if needed, and provide details (Table 38-10). If the token type is username, enable credential validation if needed for this template and provide the details.

   4. Token Mapping: Specify preferences for this template based on your token type (Table 38-11).

   5. Click Save and dismiss the confirmation window (or click Cancel without saving it).

   6. Close the definition (or edit it as described in Step 4).

3. Edit a Template: Start with the saved page you just created.

   1. Edit the template definition as needed.

   2. Click the Apply button at the top of the page to submit changes (or click Revert to undo your changes).

4. Remove a Token Validation Template:

   1. Click the desired name in the Search Results table to select the item to remove.

   2. From the Actions menu, click Delete (or click the Delete (X) command button above the table.

   3. Click the Delete button in the Confirmation window (or click No to cancel the operation).

38.5.1 About Managing Endpoints

Security Token Service Endpoint definitions consist of three categories, as shown in Figure 38-12.

Figure 38-12 Endpoints Page

Description of "Figure 38-12 Endpoints Page"

Table 38-12 describes the required Endpoints categories.

putStringProperty("/stsglobal/owsmpolicies/<index>", "<newcustom_policypath>)

putStringProperty("/stsglobal/owsmpolicies/31", "sts/newcustom_policy")

Once an Endpoint is created, you can remove it but you cannot edit the definition.

38.5.2 Managing EndPoints

Users with valid Oracle Access Management Administrator credentials can perform the following task to add, edit, or remove an Endpoint.

Prerequisites

Creating a Token Validation Template to reference

To create or delete an endpoint

1. From the Oracle Access Management Console Launch Pad, open the Security Token Service section.

2. Open the Endpoints node to display a list of existing Endpoints.

3. New Endpoint: see Table 38-12 and

   1. Click the Add (+) button above the table (or choose New Endpoint from the Actions menu).

   2. Enter the new Endpoint URI.

   3. Choose one of the Oracle WSM policies to protect this Endpoint.

   4. Choose the Validation Template to use with this Endpoint.

   5. Click Apply to submit the definition and dismiss the confirmation window (or click Revert to dismiss the page without submitting it).

   6. Close the page.

4. Remove Endpoint:

   1. Highlight a row in the Endpoints table and click the Delete (X) button (or choose Delete Selected from the Actions menu).

   2. Confirm removal (or cancel the removal).

38.6.1 About Token Issuance Policies

A Token Issuance Policy defines the rules under which a token can be issued for a resource (Relying Party Partner) based on the client's identity, with the client either being a Requester Partner or an end user. If a Requester is NOT present, it is assumed that the User (represented by the on-behalf-of (OBO) token or WSS Token) is trying to access the RelyingParty.

When issuing a token, Security Token Service will determine for which Relying Party that token is created, and it will then evaluate if the client is authorized to request the token for that Relying Party. In order to issue a token, a Token Issuance Policy must be created with the resource involved in the operation, and with possibly a condition. At runtime if the policy evaluation is successful, the token will be issued.

You can add Conditions, Rules, and Responses to this Token Issuance Policy.

38.6.2 About Managing Token Issuance Conditions and Rules

The Token Issuance Policy allows the Administrator to define conditions along with "Allow" and "Deny" rules for the policy. Each Token Issuance Policy can contain one or more conditions, and rules that determine whether access to the requested resource should be granted or denied:

• An Allow type rule specifies who is authorized to access a protected resource.

  Only partners and users listed in the Condition are granted access; everyone else is denied access to the resource.

• A Deny type rule specifies explicitly who is denied access to the protected resource.

  Only partners and users listed in the Condition are denied access; everyone else is granted access to the resource.

Managing Token Issuance Conditions is similar to managing Authorization Conditions and Rules. Figure 38-4 shows the Conditions tab of a Token Issuance Policy.

Figure 38-13 Token Issuance Policies and Conditions

Description of "Figure 38-13 Token Issuance Policies and Conditions"

Table 38-13 describes the Token Issuance Condition requirements.

38.6.3 Managing Token Issuance Policies and Conditions

Users with valid Administrator credentials can use the following procedure to add a Token Issuance Policy and Conditions to an Application Domain. When adding resources to this policy, you might want to add the UnknownRP and MissingRP resources.

Prerequisites

The Application Domain must already exist.

To manage Token Issuance Policies and conditions

1. Locate the desired domain as described in "Searching for an Existing Application Domain".

2. On the individual Application Domain page, click Token Issuance Policies tab.

3. Create a Token Issuance Policy:

   1. In the desired domain, click the Token Issuance Policies tab and then click the Create Token Issuance Policy button to open a fresh page.

   2. On the Summary page, enter a unique name and optional description.

4. Add Resources: This step presumes that the resource has been defined in the Application Domain and is ready to be added to policies.

   1. Click the Resources tab.

   2. Click the Add (+) button.

   3. Click the Search button to display a list of defined resources you can add.

   4. Click the desired resource in the results table, then click Add Selected.

   5. Repeat as needed to add any other resources to this policy.

5. Add Conditions to a Policy: The only types available are Token Requester Identity or True.

   1. Click the Conditions tab, then click the Add button on the Conditions tab to display the Add Condition window.

   2. Enter a unique name for this condition in the dialog box.

   3. Choose Token Requester Identity from the Type list.

   4. Click Add Selected.

   5. Proceed with Step 5 to add details for Token Requestor Identity. Otherwise, skip to Step 6.

6. Add Conditions Details:

   1. Click the Condition name to display Conditions: Details.

   2. From the Selected Identities table, click the Add button and choose either:

      Add Partners: In the Search field, enter criteria (or click the arrow key beside the field to find all partners); click one or more results then click Add Selected to populate the condition.

      Add Identities: Select the Store Name, select the desired Identity Type, enter search criteria and click the Search button; choose one or more results and click Add Selected to populate the condition.

   3. Click the Save button on the Condition Details panel.

7. Add Rules: Perform these steps to Allow or Deny access based on your Conditions.

   1. Click the Rules tab.

   2. Check the Rule Mode: Simple or Expression.

   3. Expression Mode: Build your expression by entering operators (Table 20-31) and choosing and inserting conditions (Table 20-30).

   4. Simple Mode: Click to Match either All or Any of the selected conditions, then using arrows for Allow (or Deny) Rule, move desired conditions from the Available Conditions column into the Selected Conditions column.

8. Click Apply and then close the Confirmation window.

9. Find (or Add) TokenServiceRP Resources in the Application Domain: See "Managing TokenServiceRP Type Resources".

38.7.1 About Managing TokenServiceRP Type Resources in Access Manager

Use the Search controls for the Application Domain to locate resources of a specific type within the domain. Figure 38-15 shows the search controls for the IAM Suite resources. Resource Type TokenServiceRP is the search criteria. The Search Results table lists all resources of this type within the Application Domain.

Figure 38-15 Search: Resource Type TokenServiceRP in Application Domain

Description of "Figure 38-15 Search: Resource Type TokenServiceRP in Application Domain"

The TokenServiceRP resources in this domain include those provided out of the box, and described earlier:

• UnknownRP resource

• MissingRP resource

38.7.2 Managing TokenServiceRP Type Resources in Application Domains

Users with valid Administrator credentials can use the following procedure to add TokenServiceRP resources to an Application Domain.

To manage TokenServiceRP Resources

1. Locate the desired Application Domain as described in "Searching for an Existing Application Domain".

2. Add TokenServiceRP Resource to the Application Domain:

   1. Click the New Resource button on the Application Domain Search page.

   2. Specify the Resource Type as TokenServiceRP.

   3. Enter a Resource URL that is the Relying Party ID for whom the token issuance policy will be defined.

   4. Click the Apply button at the top of the page to submit this and dismiss the confirmation window.

   5. See Also: "Defining Resources in an Application Domain".

3. Find TokenServiceRP Resources:

   1. In the desired Application Domain, open the Resources tab to display the Search controls.

   2. From the Resource Type, choose TokenServiceRP, and click Search.

   3. Review the Search Results table and click a name to open the Resource Definition.

38.8.1 About Making Classes Available

After writing the custom token validation and/or issuance classes, you must add Custom Token Configuration to Security Token Service to indicate when and how these classes should be used.

On the New Custom Token page only the Token Type Name is required (identified with an asterisk, *), as shown in Figure 38-16. Not all elements apply to all custom tokens. However, if you submit information that is incomplete, a dialog box appears to identify what is missing.

Figure 38-16 New Custom Token Page

After successful submission of new custom token details, the saved page is available for editing as shown in Figure 38-17.

Figure 38-17 Custom Token Definition: email

For the custom token, you must decide on the XML Element Name, XML Element Namespace, Binary Security Token Type, and so on. Table 38-14 describes the elements on a Custom Token page based on the examples in this chapter.

email_token

oracle.security.fed.sts.customtoken.email

email

oracle.security.fed.sts.tpe.providers.email.EmailTokenValidatorModuleImpl

http://email.example.com

oracle.security.fed.sts.tpe.providers.email.EmailTokenIssuerModuleImpl

Task overview: Adding custom tokens for custom classes

1. Create a JAR file containing only your custom TokenIssuerModule or TokenValidatorModule classes (or both). No XML metadata or manifest is needed.

2. Review information in Figure 38-17 and Table 38-14.

3. Add the JAR to the OAM Server hosting Security Token Service and create a new custom token, as described in Section 38.8.3, "Managing Custom Tokens".

38.8.2 About Narrowing a Search for Custom Tokens

Figure 38-18 illustrates the Custom Tokens Search controls and Results table. These appear when you double-click the Custom Tokens node in the navigation tree. By default, all currently defined custom tokens are listed when the Search Results table is displayed.

Figure 38-18 Custom Tokens Search Page and Controls

Table 38-15 describes the Custom Tokens Search elements and controls. No wild cards (*) are allowed in Custom Token searches.

Table 38-15 Custom Tokens Search Elements and Controls

Element	Description
Default Token URI	The URI that was defined for the custom token. You can enter the entire URI or only part of it. For instance, if you enter "ai" the Search Results table will display all custom tokens defined with a token URI that includes the letters "ai". Note: Wild cards are not allowed in Custom Token searches.
Search	Initiates the Search function using criteria provided in the form.
Reset	Resets the Search form with defaults only.
Search Results	Provides the results of your search based on your choices in the View menu.
Actions menu	Provides the following functions that can be performed on a selection in the results table: Note: Actions menu functions mirror command buttons above the results table. For example: New Custom Token: Click the New Custom Token button at the top of the Search page, or select New Custom Token from the menu, or click the + button above the table. Edit: Double-click a name in the Token Type Name column of the Search Results table, or select Edit from the Actions menu, or click the Edit (pencil icon) command button above the Results Table. Create Like: Select the desired row in the table and either select Create Like from the Actions menu, or click the Create Like command button above the table Remove: Select the desired row in the table and either select Delete from the Actions menu, or click the Delete (X) command button above the table.
View menu	Provides functions you can use to display various information in the results table:
	Controls affecting the ordering of items listed in the results table: Ascending Descending

38.8.3 Managing Custom Tokens

Users with valid Administrator credentials can use the procedure in this section to manage custom tokens for custom Token Module classes.

The following procedure includes steps to add, edit, and delete custom tokens or attributes of a custom token. Skip any steps that you do not need.

Prerequisites

Refer to the developer creating the custom tokens and the Oracle Fusion Middleware Developer's Guide for Oracle Access Management for details about:

Writing a TokenValidatorModule Class

Writing a TokenIssuanceModule Class

To make custom classes available

1. Create and add the JAR containing your Issuance and Validation classes to the OAM Server hosting Security Token Service using one of these methods:

   • Add the custom token jar and the sts-common.jar that is available in $DOMAIN_HOME/config/fmwconfig/mbeans/oam to the Managed Server classpath by editing the startup script.

   • Add the custom token jar and the sts-common.jar that is available in $DOMAIN_HOME/config/fmwconfig/mbeans/oam to the $DOMAIN_HOME/lib directory to automatically add these jars to the Managed Server classpath.

   • Restart the OAM Server.

2. New Custom Token: From the Oracle Access Management Console Launch Pad, click the Security Token Service link.

   1. Open the Custom Tokens node to open the Search controls.

   2. Click the New Custom Token button.

   3. Fill in the New Custom Token page with details for your custom classes (Table 38-14).

   4. Click Save and dismiss the confirmation window (or click Cancel to dismiss the page without submitting it).

   5. Close the page (or edit as described in Step 4).

   6. Proceed to Step 4, if needed, or to "Managing a Custom Security Token Service Configuration".

3. Find Custom Tokens: From the Oracle Access Management Console Launch Pad, click the Security Token Service link.

   1. Find All: Click the Search button and view the results table with all custom tokens listed.

   2. Narrow the Search: Enter some or all characters in the desired Default Token URI, click the Search Button, and review the results table.

   3. Reset the Search Form: Click the Reset button.

4. Edit Custom Token Configuration: Start with the saved page you just created.

   Alternatively: Use Step 3 to find the desired Custom Token, then double-click the name in the Search Results table to open the page.

   1. In the named Custom Token page, click the appropriate field and edit as needed.

   2. Add Attributes: Click the Add (+) icon for the Attributes table, enter the Attribute Name and an Attribute Type (Table 38-14).

   3. Remove Attributes: From the Attributes table, click the row containing the attribute to remove, click the Delete (X) icon for the table, and dismiss the Confirmation window.

   4. Apply Changes: Click the Apply button at the top of the page to submit changes.

5. Remove a Custom Token:

   1. Click the desired name in the Search Results table to select the item to remove.

   2. From the Actions menu, click Delete (or click the Delete (X) command button above the table.

   3. Click the Delete button in the Confirmation window (or click No to cancel the operation).

38.9.1 Creating the Validation Template

Users with valid Oracle Access Management Administrator credentials can perform the following task to create a Validation Template with a Token Protocol of Webservice Trust to map the token to the requester.

The template in this example can be used for the module classes described earlier in this chapter. Full implementation details are shown in the following figures. As you review these, notice how specifications for this template reference the module class code:

• Figure 38-19, "General Details: email-wstrust-valid-temp"

• Figure 38-20, "Token Mapping: email-wstrust-valid-temp"

Figure 38-19 General Details: email-wstrust-valid-temp

Figure 38-20 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 Management Console Launch Pad
   Security Token Service
   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.

   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".

38.9.2 Creating the Issuance Template for a Custom Token

This is a server side configuration. Users with valid Oracle Access Management 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 38-21, "General Details: email-issuance-temp"

• Figure 38-22, "Issuance Properties: email-issuance-temp"

Figure 38-21 General Details: email-issuance-temp

When you have a custom token type deployed, the Issuance Properties are tailored to accommodate the custom token. For instance, the custom email token type was chosen for the issuance template show in Figure 38-22.

Figure 38-22 Issuance Properties: email-issuance-temp

This procedure produces a companion Issuance Template for the custom module classes in this chapter. For the example:

• Ignore the Token Encryption Algorithm, which is not used for the custom token type: email.

• Fill in a value for the Custom Token Attribute, which is populated from the custom token code.

To create the Issuance Template for the custom module classes

1. Find existing Token Issuance Templates.:

   
   Oracle Access Management Console Launch Pad
   Security Token Service
   Token Issuance Templates
   Search button (with or without filling in search criteria)
   

2. New Token Issuance Template:

   1. Click the New Issuance Template button in the upper-right corner (or click the Add (+) command button above the Search Results table).

   2. General: Set the following for use with the custom token in this chapter.

      
      Issuance Template Name: email-issuance-temp
      Token Type: email
      

   3. Click Save and dismiss the confirmation window (or click Cancel without saving).

   4. Issuance Properties: Set the following for use with the custom token in this chapter.

      
      Custom Token Attribute Value: world
      

   5. Click Apply and dismiss the confirmation window (or click Revert without saving it).

   6. Close the definition (or edit it as described in Step 4).

3. Edit a Template: Find the desired template, edit details, and click Apply.

   Alternatively: Use Step 3 to find the desired template and click the name in the Search Results table to display the definition.

38.9.3 Adding the Custom Token to a Requester Profile

You can either edit an existing requester profile to add your custom token to the Token Type Configuration table, or create a new requester profile to use with the custom token. Either way, configure:

• Token Type: email (your custom token)

• Validation Template: email-wstrust-valid-temp

Prerequisites

Your Custom Token and Validation Template must be defined.

To create or edit a requester profile for the custom token

1. From the Oracle Access Management Console Launch Pad, click the Security Token Service link.

2. In the navigation tree, open the Partner Profiles node and double-click the Requestor Profiles node to display a list of existing profiles

3. Existing Profile:

   1. In the Search Results table of the Requester Profiles page, click the name of the desired profiles.

   2. Token and Attributes: Fill in the following details for the custom token in this chapter and then click the Save button at the top of the page.

      
      Token type: email
      Validation Template: email-wstrust-valid-temp
      

   3. Click Save, dismiss the confirmation window, and close the page (or click Cancel to dismiss the page without submitting it).

   4. Proceed to "Adding the Custom Token to a Requester Profile".

4. New Profile: Click the New Requester Profile button to display the New Partner Profile page where you enter details:

   1. General: Fill in the following details for the custom token in this chapter and then click the Next button at the top of the page.

      
      Profile ID: unique_requesterprofile_name
      Default Relying Party Profile: unique_relyingparty_name
      

   2. Add Token Type Configuration: Fill in the following details for the custom token in this chapter and then click the Save button at the top of the page.

      
      Token type: email
      Validation Template: email-wstrust-valid-temp
      

   3. Proceed to "Adding the Custom Token to a Requester Profile".

38.9.4 Adding the Custom Token to the Relying Party Profile

You can either edit an existing Relying Party profile, or create a new one to issue the custom token by default, and refer to the Issuance Template and related information. Either way, configure:

• Default token to issue: email (your custom token)

• Issuance Template: email-issuance-temp

Prerequisites

Your Custom Token and Issuance Template must be defined.

To edit the requester profile for the custom module classes

1. From the Oracle Access Management Console Launch Pad, click the Security Token Service link.

2. In the navigation tree, open the Partner Profiles node and double-click the Relying Party Profiles node to display a list of existing profiles.

3. Existing Profile:

   1. In the Search Results table of the Relying Party Profiles page, click the name of the desired profile.

   2. Click the Token and Attributes tab.

   3. Token Type Configuration: Click the Add (+) button above the Token Type Configuration table and enter the following details:

      
      Token type: email
      Issuance Template: email-issuance-temp
      

   4. Attributes: Click the Add (+) button above the Attributes table and define the following:

      
      Attribute name: mail
      Store Type: Userstore
      Include in Token: (check to enable)
      Encryption (leave blank)
      Value (leave blank)
      

   5. Click Apply, dismiss the confirmation window, and close the page (or click Cancel to dismiss the page without submitting it).

4. New Profile: Click the New Relying Party Profile button to display the New Partner Profile page where you enter details:

   1. General: Fill in the following details for the custom token in this chapter and then click the Next button at the top of the page.

      
      Profile ID: unique_relyingparty-name
      Default Token: email
      

   2. Click the Token and Attributes tab and perform Steps 2c and 2d, then click Apply.

38.9.5 Mapping the Token to a Requestor

If you don't have a Username Validation Template (username-wss-valid-template), use the Oracle Access Management Console to create one to map the token to the requester.

Validation Template Name: username-wss-valid-template

Token Type: Username

Proceed to "Creating an /wssuser EndPoint"

38.9.6 Creating an /wssuser EndPoint

Prerequisites

Mapping the Token to a Requestor

To create an endpoint

1. From the Oracle Access Management Console System Configuration tab, open the Security Token Service section.

2. Double-click the Endpoints node to display a list of existing Endpoints.

3. New Endpoint:

   1. Click the Add (+) button above the table (or choose New Endpoint from the Actions menu).

   2. Enter the new Endpoint URI: /wssuser

   3. Choose the Oracle WSM policy: sts/wss_username_service_policy

   4. Choose the Validation Template: username-wss-validation-template.

   5. Click Apply to submit the definition and dismiss the confirmation window (or click Revert to dismiss the page without submitting it).

   6. Close the page.