Oracle VirtualBox (OVB) deploy tasks
Testing with to Oracle Virtual includes the following tasks:
Important
Oracle VirtualBox is only supported for development and test use. Okta does not support deploying Access Gateway into Oracle Virtual Box 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
All Access Gateway deployments require a set of common tasks:
| Task(s) | Description |
| Set Access Gateway instance hostname | Access Gateway specifies a known gateway hostname which can be changed. |
| [Optional] Set Access Gateway instance IP address | Many installations require Access Gateway to use a fixed known IP address. |
| [Optional] Set Access Gateway DNS Servers | Many installations use a split DNS process where multiple DNS servers are required. |
|
[Optional] Set Access Gateway proxy server |
Many installations require a proxy server for Access Gateway. |
| Determine Access Gateway IP address for non-AWS instances
Configure admin /etc/hosts entry Configure Access Gateway DNS |
Determine Access Gateway IP address. Configure required /etc/hosts admin entry. Configure required DNS entries. |
| Initialize Access Gateway Admin UI console | Initialize the cookie domain and instance hostname. |
| Configure your Okta tenant as an identity provider | Configure Okta tenant as an identify provider. |
| Configure SAML access to from your Okta tenant | Configure Okta tenant to allow access to Access Gateway using SAML. |
| Review security best practices | Examine and execute a set of common Access Gateway security best practices. |
Important
When creating a set of Access Gateway nodes for use in a high availability cluster, ensure that nodes are named appropriately.
Also, node names must be resolvable between Access Gateway instances before configuring high availability.