Oracle Security Token Service High Availability Architecture

Configuring High Availability for Identity Management Components 8-125 ■ Oracle Security Token Service Implementation Scenarios ■ Managing Oracle Security Token Service Settings and Set Up ■ Managing Oracle Security Token Service Certificates and Keys ■ Managing Templates, Endpoints, and Policies ■ Managing Token Service Partners and Partner Profiles For information on patching, see Migrating Oracle Access Manager 11.1.1.3.0 to 11.1.1.5.0 This section includes the following topics: ■ Section 8.8.3.1, Oracle Security Token Service High Availability Architecture ■ Section 8.8.3.2, Oracle Security Token Service Component Characteristics ■ Section 8.8.3.3, Oracle Security Token Service High Availability Configuration Steps ■ Section 8.8.3.4, Validating Oracle Security Token Service High Availability ■ Section 8.8.3.5, Oracle Security Token Service Failover and Expected Behavior ■ Section 8.8.3.6, Disabling and Enabling Oracle Security Token Service ■ Section 8.8.3.7, Troubleshooting Oracle Security Token Service ■ Section 8.8.3.8, Log File Location

8.8.3.1 Oracle Security Token Service High Availability Architecture

The following figure shows Oracle Security Token Service in a high availability architecture: Figure 8–14 Oracle Security Token Service High Availability Architecture 8-126 Oracle Fusion Middleware High Availability Guide This figure shows a two-node deployment of Oracle Access ManagerOracle Security Token Service components. This section provides details about an Oracle Security Token Service high availability deployment. For more details about the overall Oracle Access Manager high availability architecture, which is deployed as part of, see Section 8.8.2.1, Oracle Access Manager High Availability Architecture . Security Token Service is the server side component that implements the WS-Trust protocol support. The load balancer receives token requests and routes them to the Security Token Service STS. The Oracle Access Manager Administration console is a J2EE application that provides services to manage the Oracle Security Token Service deployment. As part of the OAM deployment, Administration Console must deploy to the Weblogic AdminServer. In Oracle Security Token Service, each WLS domain supports one Oracle Security Token Service cluster. OAMOracle Security Token Service clusters cannot span WebLogic Server domains. Oracle Security Token Service is primarily based on the OASIS WS-Trust protocol. However, Oracle Security Token Service delegates the processing of other WS- protocols present in the SOAP message to the JAX-WS stack. Oracle recommends using external LBRs for inbound HTTPSOAP connections. Outbound external connections to LDAP servers are load balanced with support for connection failover.

8.8.3.1.1 Clients and Client Connections Web Service clients that implement the WS-Trust

protocol interact with Oracle Security Token Service to issue or validate tokens. Clients designed to interact with an STS server, such as OWSM Client, as part of a Web Service call to a Relying Party can invoke Oracle Security Token Service. The client connection process is as follows: 1. The Web Service client sends a SOAP message over http or https. The WSS protocol protects the message. The payload contains a WS-Trust request RST indicating the operation to perform, which kind of token to issue or validate, and additional information about the token characteristics. 2. The server processes the request and sends a response over the same channel the server received it on. The WSS protocol protects the message. The payload contains a WS-Trust response RSTRC if the processing was successful or a SOAP fault if an error occurs.

8.8.3.1.2 Cluster Wide Configuration Changes Each Oracle Security Token Service Access

Server instance is a peer of other instances with no inter-instance communication. Because all initialization happens before the Server is ready to receive requests combined with built in throttling capabilities, the WebLogic Server handles surge conditions gracefully without any significant effect on Oracle Security Token Service Access Server performance characteristics. When the cluster stops, the Oracle Security Token Service denies new requests and permits existing requests to complete before the Access Server application shuts down. If a forced shutdown occurs, Oracle Security Token Service can recover for any corruptedinvalid data that the shutdown causes. Propagation of configuration changes to all the cluster members is based on a distribution mechanism that leverages the Coherence distributed object cache. The coherence layer notifies all Oracle Security Token Service components of change Configuring High Availability for Identity Management Components 8-127 events. The components then uptakes these change events. OAM components reload their entire configuration every time a change happens.

8.8.3.2 Oracle Security Token Service Component Characteristics