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. Theoption 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:
You can inject this information by setting theto 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> .
Select the policy container, then click.
Specify a name for the policy, selectfor 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 thesection, 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 4.3, Configuring an Authentication Header Policy.> , or . For more information, see
LDAP Attribute: Injects the value of the selected attribute. For Active Directory servers, specify the SAMAccountName attribute for the username. If the attribute you require does not appear in the list, clickto add the attribute.
Theoption allows you to determine when to send a query to the LDAP server to verify the current value of the attribute. Because querying the LDAP server slows down the processing of a policy, LDAP attribute values are normally cached for the user session.
Change the value of this option from session to a more frequent interval only on those attributes that are critical to the security of your system or to the design of your work flow. You can select to cache the value for the session, for the request, or for a time interval varying from 5 seconds to 60 minutes. For more information, see Section 4.1.1, Using the Refresh Data Option.
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 NetIQ Access Manager 3.1 SP5 Identity Server Guide.
Proxy Session Cookie: Injects the session cookie associated with the user.
Roles: 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 5.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, see
Theoption allows you to determine when to send a query to verify the current value of the secret. Because querying slows down the processing of a policy, secret values are normally cached for the user session.
Change the value of this option from session to a more frequent interval only on those secrets that are critical to the security of your system or to the design of your work flow. You can select to cache the value for the session, for the request, or for a time interval varying from 5 seconds to 60 minutes. For more information, see Section 4.1.1, Using the Refresh Data Option.
String 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.
Data Extension: (Conditional) If you have installed a data extension for Identity Injection policies, this option injects the value that the extension retrieves. For more information about creating a data extension, see Novell Access Manager Developer Tools and Examples.
To add multiple tag and value pairs to the custom name, clickin 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.
NDAP Partial Dot Notation: Specifies eDirectory typeless dot notation.
NDAP Leading Partial Dot Notation: Specifies eDirectory typeless leading dot notation.
NDAP Fully Qualified Partial Dot Notation: Indicates eDirectory typed dot notation.
NDAP Fully Qualified Leading Dot Notation: Indicates eDirectory typed leading dot notation.
(Optional) To add additional custom header actions, click, then select or use the icon and modify the new entry.
To save the policy, clicktwice, then click .