Getting Started with Okta Access Gateway

Okta Access Gateway allows you to secure access to your on-premises apps and protect your hybrid cloud. All without changing how your apps work today. Use Okta Access Gateway to connect Okta to on-premises applications that use header-based, KerberosKerberos is a computer-network authentication protocol that works on the basis of tickets to allow nodes communicating over a non-secure network to prove their identity to one another in a secure manner., or URL-based authorization.

Okta Access Gateway is one of several elements required to secure applications, including:

Access Gateway Components

The Access Gateway solution is implemented within a customer’s infrastructure, and can be deployed in the cloud, on-premise, or within a hybrid solution. It’s provided by Okta as an Open Virtual Appliance (.ova) file.

A deployment of Access Gateway includes:

  • Your Users - Represented by a directory service, often your Okta Org.
  • Okta Org - Your Okta organization.
  • Load Balancer(s) - One or more load balancers
  • Access Gateway instances - One or more access gateway instances.
  • Application Resources - One or more protected resources.

In addition, Access Gateway can be made fault tolerant through the use of secondary stand-by implementations.

Example Architectures

Typical Tasks

The following include typical first tasks performed by an administrator to install and configure an initial instance of Access Gateway.


Tracks are pathways through the Access Gateway documentation