The following topics explain how to use policy responses in Access Manager in the context of federation policies:
A policy can optionally include one or more authentication responses, or authorization responses, or both. You can configure the use of assertion attributes when setting up Access Manager policy responses with Identity Federation.
You use assertion attributes as follows:
Authorization policy conditions
Response attributes as HTTP headers
Response attributes for identity context
Figure 40-7 shows the Response configuration tab for an authorization policy:
Figure 40-7 Authorization Policy Response Tab
Table 40-6 describes the elements for a policy response.
Table 40-6 Policy Response Elements
This is a unique name to distinguish this response from other responses that use the same mechanism (type).
This is the mechanism used to convey the response form of the action to be taken with the value string. Select Assertion Attribute.
This is the response expression, set as a variable. To provide the federation data as response attributes in the authentication or authorization policy, the values can reference:
You can use the Oracle Access Management Console to configure policy responses with assertion attributes.
Identity Federation conditions and responses must be specified separately because they are used for different tasks.
For example, if the identity provider sends a role assertion and the service provider wanted to only allow people who had a role of
sales to gain access to the resource, you add a condition as follows:
The Condition Namespace is "Session".
The Name is "fed.attr.role".
The Operator is set to EQUALS.
Value is "sales".
A condition is used to control access to a resource within Access Manager.
Replace the role in this example to the actual SAML asserted attribute.
If you want to use the standard SAML NameID value as the condition, then the value is "attr.fed.nameidvalue".
A response, on the other hand, enables you to pass an asserted attribute to the application.For example, if you wanted to pass the asserted attribute
role to a back-end application in an HTTP header, you would:
Go to the Response tab.
Add a Header, name
Role (this is the name of the HTTP header).
The value would be
Then replace the role in this example to correspond to the SAML asserted attribute.
To view or configure responses with assertion attributes:
See Table 40-6 for details.
Figure 40-8 shows an example of federation response attribute configuration.
Figure 40-8 Adding a Federation Response Attribute to an AuthZ Policy