Access Gateway deployment tasks
This topic describes how to deploy Access Gateway in one of the supported environments.
You must also address capacity planning as part of your deployment. See Capacity planning and Access Gateway.
Perform these tasks in the order shown here:
| Task | Description |
|---|---|
| Download the Access Gateway virtual appliance file |
Select and download the virtual appliance file for the environment you're using. Access Gateway supports the following production environments:
|
| Deploy the image into the virtual environment. | Import the virtual appliance file into the target virtual environment. The steps are different for each virtual environment. For development and testing purposes, VMWare and Oracle Virtual Box are the simplest deployment environments. See Deploy Access Gateway for development environments. |
| Reset the instance |
Reset the Access Gateway instance after you've imported it into the virtual environment. Access the instance using the Access Gateway Management console and run the reset command. See Reset Access Gateway: command line. |
| Determine or manage the Access Gateway IP address |
This IP address is used to access the instance to the Identity Provider and other settings. Depending on environment requirements Access Gateway can use a specific or assigned IP address. See Add admin host entries. |
| Initialize the Access Gateway Admin UI console |
Assign Access Gateway a cookie domain. This domain represents the general domain that the gateway is protecting. See Initialize the Access Gateway Admin UI console. |
| Associate Access Gateway with an Okta org | All Access Gateway instances use an Okta org to manage applications, end users, and the access of one from the other. See Configure an Identity Provider in Access Gateway. |
See Deploy Access Gateway for development environments for instructions unique to development environments.
Related topics
Access Gateway deployment prerequisites