Typical Deployment Scenario Reference Server Footprint Topology

Planning Oracle Identity Federation Deployment 2-29 Figure 2–11 A Typical Federation Deployment Architecture

2.6.3 Reference Server Footprint

The following hardware and equipment is recommended for a baseline Oracle Identity Federation deployment, for an environment supporting up to 2000 concurrent users: ■ Any supported server-class machine and operating system for Oracle Identity Federation. See the certification matrix for a list of certified platforms for Oracle Identity Federation. Failover scenarios would double the number of machines required. Use a minimum of two Oracle Identity Federation servers, on separate machines, for redundancy. ■ Server footprint: – 2-4 GB memory 4GB recommended – Minimum of 2 CPUs per machine ■ If a proxy server is being used, follow the vendor-specific sizing recommendations.

2.6.4 Topology

Figure 2–12 shows the recommended topology for an Oracle Identity Federation deployment in SP mode in which Oracle HTTP Server serves up a provider application that is protected by a webgate. 2-30 Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation Figure 2–12 Sample Topology for Oracle Identity Federation

2.7 Implementation Checklist

The following checklist summarizes the key items for planning an Oracle Identity Federation installation and provides the essential starting point for deployment. Note: Liberty 1.x support is deprecated. Table 2–4 Implementation Checklist Planning Item Recommended Proposed Value Notes ArchitectureBasic Configuration role played IdP, SP, or both protocol Liberty 1.1, Liberty 1.2, SAML 2.0, or any combination of the three. SAML 1.0, SAML 1.1, and WS-Federation. Planning Oracle Identity Federation Deployment 2-31 Repository Specify repository for the user data and federation persistent data. LDAP server hostname for example, ldap.mydomain.com LDAP server port number for example, 389 LDAP server access credentials for example, Bind DN = {cn=orcladmin}, Password = {mysecret} Base DN for example, dc=mydomain,dc=com federation record context for example, cn=fed,dc=mydomain ,dc=com federation schema update 1 This information must be provided at the time of installation. transient data store Specify repository for transient data: RDBMS or in-memory. Configuration data store Specify repository for transient data: RDBMS or File IdP Profiles Bindings Use a row for each combination enabled. SP Profiles Bindings Use a row for each combination enabled. SSL Encryption EnabledDisabled Java keystore for SSL For information about setting up SSL, see Section 8.1, Configuring SSL for Oracle Identity Federation . Certificates signing Specify location of PKCS 12 wallet for signing key pair. encryption Specify location of PKCS 12 wallet for encryption key pair. Table 2–4 Cont. Implementation Checklist Planning Item Recommended Proposed Value Notes