High Availability Best Practices
The following are a list of best practices and considerations for configuring Access Gateway High Availability:
- Before configuring a High Availability cluster, be sure to reset keys for all cluster members, including adminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. and worker instances, using System > High Availability > Reset Keys.
- Always ensure that new Access Gateway instances have set their hostname. Instances default to oag.okta.com as hostname. Use the Access Gateway command line interface System > Hostname command to change or verify the current hostname.
- When initially configuring an Access Gateway instance use the System > Reset command to reset the instance to an initial state.
See Command Line Management Console Reference for complete details of all Access Gateway command line operations.
When configuring an Access Gateway high availability cluster, you may add your Okta tenant as an idPAn acronym for Identity Provider. It is a service that manages end user accounts analogous to user directories such as LDAP and Active Directory, and can send SAML responses to SPs to authenticate end users. Within this scenario, the IdP is Okta. at any time. In addition, you may also add applications any time.