Some Web applications require more than a name and a value to be injected into the custom header. Sometimes they require a custom name, a tag, and a value. Sometimes the application requires a custom name with multiple tags and values. The
option provides you with the flexibility to add such values to the custom header. For example, your application could be expecting the following custom header with tag:X-Custom_Role Role=Manager
You can inject this information by setting the
to X-Custom, the to Role, and the to Manager. The value can be set as a static variable or you can retrieve it from various sources such as a Liberty User Profile attribute or the roles assigned to the current user.In the Administration Console, click
> > .Specify a name for the policy, select
for the type, then click .(Optional) Specify a description for the injection policy. This is useful if you plan to create multiple custom header policies to be used for multiple resources.
In the
section, click , then select .Fill in the following fields:
Custom Header Name: Specify the name that the application expects. If your application requires the X- prefix, make sure you include the prefix in this field.
Tag Name: Specify the tag name that the application expects.
Tag Value: Specify the value. Select from the following data types:
Authentication Contract: Injects the URI of a local authentication contract that the user used for authentication.
Client IP: Injects the IP address associated with the user.
Credential Profile: Injects the credentials that the user specified at login. You can select Section 29.3, Configuring an Authentication Header Policy.
> , or . For more information, seeLDAP Attribute: Injects the value of the selected attribute.
Liberty User Profile: Injects the value of the selected attribute. If no profile attributes are available, you have not enabled their use in the Identity Server configuration. See Section 12.2, Enabling Web Services and Profiles.
Proxy Session Cookie: Injects the session cookie associated with the user.
Roles for Current User: Injects the roles that have been assigned to the user.
Shared Secret: Injects a value that has been stored in the selected shared secret store. The name specified as the Tag Name must match the name of a name/value pair stored in the shared secret.
You can create your own value. Click Section 30.4, Creating and Managing Shared Secrets.
, specify a display name for the store, and the Access Manager creates the store. Select the store, click , specify a name for the attribute, then click . The name must match the expected Tag Name. The store can contain one name/value pair or a collection of name/value pairs. For more information, seeString Constant: Injects a static value that you specify in the text box. This value is used by all users who access the resources assigned to this policy.
To add multiple tag and value pairs to the custom name, click
in the section.Use the up-arrow and down-arrow buttons to order the tags.
Specify the format for the value:
Multi-Value Separator: Select a value separator, if the value type you have select is multi-valued. For example,
can contain multiple values.DN Format: If the value is a DN, select the format for the DN:
LDAP: Specifies LDAP typed, comma notation: For example:
cn=jsmith,ou=Sales,o=novell
NDAP Partial Dot Notation: Specifies eDirectory typeless, dot notation: For example:
jsmith.sales.novell
NDAP Leading Partial Dot Notation: Specifies eDirectory typeless, leading dot notation.
.jsmith.sales.novell
NDAP Fully Qualified Partial Dot Notation: Indicates eDirectory typed, dot notation. For example:
cn=jsmith.ou=Sales.o=novell
To save the policy, click
twice, then click .