Oracle VirtualBox deployment tasks
Access Gateway only supports using Oracle VirtualBox for development and test use. Okta doesn't support deploying Access Gateway to Oracle VirtualBox for production use.
Oracle VirtualBox deployment tasks
|
Task |
Description |
|---|---|
| Download the latest OVA image | Download current version of the Access Gateway OVA. |
| Deploy OVA to Oracle VirtualBox | Import the downloaded OVA into Oracle VirtualBox. |
Post-deployment tasks
|
Task |
Description |
|---|---|
| Reset Access Gateway and verify its configuration | Initialize Access Gateway after its first boot. |
| Set the Access Gateway instance hostname | Set a hostname for Access Gateway. |
| Optional. Set the Access Gateway instance IP address | Configure a fixed IP address for Access Gateway. |
| Optional. Set Access Gateway DNS servers | Configure Access Gateway to use a split DNS process where multiple DNS servers are used. |
| Optional. Set an Access Gateway proxy server | Configure Access Gateway to be used with a proxy server. |
| Determine the Access Gateway IP address |
Determine the Access Gateway IP address for non-AWS instances. Configure the required admin entry in the local hosts file. Configure the required DNS entries. |
| Initialize the Access Gateway Admin UI console | Initialize the cookie domain and instance hostname. |
| Configure an Identity Provider in Access Gateway | Configure an Okta org as an Identity Provider. |
| Add an Access Gateway Admin UI console app | Configure an Okta org to allow access to Access Gateway using SAML. |
| Access Gateway security best practices | Examine and execute a set of common Access Gateway security best practices. |
Ensure that you appropriately name your Access Gateway nodes when you create them for use in a high-availability cluster. These names must be resolvable between Access Gateway instances before you configure high availability.