Authorization process

The authorization process determines whether an authenticated user has the right to perform an operation on a specific resource in a secure domain. When WebSEAL enforces security in a secure domain, each user must provide proof of its identity. In turn, ISAM security policy determines whether that user is permitted to perform an operation on a requested resource. Because access to every Web resource in a secure domain is controlled by WebSEAL, WebSEAL's requirements for authentication and authorization can provide comprehensive network security. In security systems, authorization is distinct from authentication. Authentication can validate the identity of a user, but says nothing about the user's right to perform operations on a protected resource. In the ISAM authorization model, authorization policy is implemented independently of the mechanism used for user authentication. Users can authenticate their identity by using either public and private key, secret key, or customer-defined mechanisms. Part of the authentication process involves the creation of a credential describing the identity of the user. Authorization decisions that are made by an authorization service are based on user credentials.

The resources in a secure domain receive a level of protection as dictated by the security policy for the domain. The security policy defines the legitimate participants of the secure domain and the degree of protection that surrounds each resource being protected. The authorization process consists of the following basic components:

• A resource manager is responsible for implementing the requested operation when authorization is granted. WebSEAL is a resource manager.

  A component of the resource manager is a policy enforcer that directs the request to the authorization service for processing. Traditional applications bundle the policy enforcer and resource manager into one process. Examples of this structure include WebSEAL and third-party applications.

• An authorization service performs the decision-making action on the request.

Authorization process

1. A request for a resource from an authenticated user is directed to the resource manager and intercepted by the policy enforcer process.

   The resource manager can be WebSEAL (for HTTP, HTTPS access) or a third-party application.

2. The policy enforcer process uses the ISAM authorization API to call the authorization service for an authorization decision.

3. The authorization service performs an authorization check on the resource, represented as an object in the protected object space.
   1. POPs are checked first.
   2. Next the ACL policy attached to the object is checked against the client's credentials.
   3. Finally, POPs enforced by the resource manager are checked.

4. The decision to accept or deny the request is returned as a recommendation to the resource manager (through the policy enforcer).

5. If the request is finally approved, the resource manager passes the request on to the application responsible for the resource.

6. The user receives the results of the requested operation.

Parent topic: IBM Security Verify Access WebSEAL overview

Related concepts

• Introduction to IBM Security Verify Access
• WebSEAL introduction
• ISAM appliance
• WebSEAL functionality on the appliance
• Security concepts for a WebSEAL deployment
• Security policy planning
• Content types and levels of protection
• WebSEAL authentication
• Standard WebSEAL junctions
• Web space scalability