# Oracle Access Manager Authorization

## Contents
Overview Configuration

## Overview
This filter enables you to authorize an authenticated user for a particular resource against Oracle Access Manager (OAM). The user must first have been authenticated to OAM using the HTTP Basic or HTTP Digest filter. After successful authentication, OAM issues a Single Sign On (SSO) token, which can then be used instead of the user name and password.
## Configuration
Configure the following fields to authorize a user for a particular resource against Oracle Access Manager: Name: Enter a descriptive name for this filter. Attribute Containing SSO Token: Enter the name of the message attribute that contains the user's SSO token. This attribute will have been populated when authenticating to Oracle Access Manager using the HTTP Basic or HTTP Digest filter. By default, the SSO token is stored in the `oracle.sso.token` message attribute. Resource Type: Enter the type of the resource for which you are requesting access. For example, when seeking access to a Web-based URL, specify `http`. Resource Name: Enter the name of the resource for which the user is requesting access. By default, this field is set to `//hostname${http.request.uri}`, which contains the original path requested by the client. Operation: In most access management products, it is common to authorize users for a limited set of actions on the requested resource. For example, users with management roles may be able to write (HTTP POST) to a certain Web Service, but users with more junior roles might only have read access (HTTP GET) to the same service. You can use this field to specify the operation that you want to grant the user access to on the specified resource. By default, this field is set to the `http.request.verb` message attribute, which contains the HTTP verb used by the client to sent the message to the Enterprise Gateway (for example, POST).