Access Gateway supported applications

When creating an application configuration in Okta Access Gateway, there are various application templates available to speed up the configuration process. The different application templates are described here for reference.

See Supported technologies for a list of current supported application versions.

Application types

Important Note

Important

Okta Access Gateway supports a maximum of 600 integrated applications.

Application type Description Configuration details

Sample Cookie

Out of the box Access Gateway application based on cookies.

This sample demonstrates passing data as cookie content. When executed, the application prints out all passed cookie data. See Sample cookie application.

Sample Header

Out of the box Access Gateway header web application type with IDCS attributes.

This sample demonstrates passing data as headers to an application. When executed, the application prints all passed header fields. See Add a sample header application.

Sample Policy

Out of the box Access Gateway policy application type

This sample demonstrates creating a set of example policies.  When executed, the application performs tests against these policies. See Managing Application Policy for more information about Access Gateway policies and policy management.

Sample Proxy

Out of the box Access Gateway policy application type

This sample demonstrates a basic proxy application. When executed, the application displays simulated access to the back-end proxy host. See Sample proxy application.

Header Based

A header web application type

This configuration is best used for applications that don't require specific settings. Access Gateway provides SSO using HTTP headers to this application. See Add a generic header application.

Supported versions:

  • Any that use HTTP Headers.

Microsoft IIS IWA
Microsoft OWA IWA
Microsoft Sharepoint IWA

Microsoft Kerberos based application type

The Microsoft IWA-based application types enable Access Gateway to work with Kerberos-based back-end applications. See Add a Kerberos App.

Supported versions:

  • Microsoft IIS IWA -iIS 7 or later
  • Microsoft OWA IWA - IIS 7 or later

No-auth

No authentication application

The no-auth configuration enables an application to be reverse proxied by Access Gateway without any authentication. This configuration is best used when exposing internal applications to the internet. See Add a no-auth app to Access Gateway.

Oracle Access Gate

Oracle Access Gate application type

The Oracle Access Gate app enables Access Gateway to SSO with Oracle E-Business applications. By default this application passes the USER_NAME and USER_ORCLGUID headers to the Oracle Access Gate. It is required that Oracle Access Gatehas been configured to enable SSO. Contact Oracle for assistance with Oracle Access GateSSO configuration.
See Add an Oracle Access Gate Application.

Supported versions:

  • v10g or later

Oracle Agile PLM

Out of the box Access GatewayAgile PLM application type

The Oracle Agile PLM app enables Access Gateway to SSO with Agile PLM applications. By default this application passes the REMOTE-USER header to the Agile PLM. Contact Oracle for assistance with Agile PLM SSO configuration.
See Add an Oracle Agile PLM Application.

Supported versions:

  • v9 or later

Oracle Application Express

Out of the box Access Gateway Oracle Application Express application type

The Oracle Application Express app enables Access Gateway to SSO with Oracle Application Express applications.
See Add an Oracle Application Express application.

Supported versions:

  • v10g or later

Oracle Demantra

Out of the box Access Gateway Oracle Demantra application type

The Oracle Demantra app enables Access Gateway to SSO with Oracle Demantra applications.

See Add an Oracle Demantra Application.

Supported versions:

  • v10g or later

Oracle BI Enterprise Edition

Out of the box Access Gateway Oracle BI Enterprise Edition application type

The Oracle BI Enterprise Edition app enables Access Gateway to SSO with Oracle Business Intelligence Enterprise Edition applications. By default this application passes the OAM_REMOTE_USER header to the OBIEE. Contact Oracle for assistance with OBIEE SSO configuration.
See Add an Oracle BI Enterprise Edition application.

Supported versions:

  • Oracle BI Enterprise Edition 11g with latest patchset
  • Oracle BI Enterprise Edition 12.1
  • Oracle BI Enterprise Edition 12.2

Oracle EBS R12.1
Oracle EBS R12.2
Oracle EBS Rapid SSO

Oracle E-Business Suite R12.1
Oracle E-Business Suite R12.2
Oracle E-Business SSO

The EBS configurations enable Access Gateway to SSO with Oracle E-Business applications. By default this application passes the USER_NAME and USER_ORCLGUID headers to the Oracle Access Gate and EBS application. E-Business must have been configured to enable SSO. Contact Oracle for assistance with E-Business SSO configuration. See Add an Oracle EBS application.

Supported versions:

  • v12.1
  • v12.2

Oracle Forms

Oracle Forms application

The Oracle Forms app enables Access Gateway to SSO with Oracle Forms applications.
See Add an Oracle Forms App.

Supported versions:

  • v10g or later

Oracle Hyperion

Oracle Hyperion application

The Hyperion configuration enables Access Gateway to SSO with Oracle Hyperion applications. By default this application passes the HYPLOGIN header to the Hyperion application. Hyperion must have been configured to enable SSO. Contact Oracle for assistance with Hyperion SSO configuration. SeeAdd an Oracle Hyperion Application

Supported versions:

  • v11g

Oracle JD Edwards EnterpriseOne

Out of the box Access Gateway JD Edwards application type

The Oracle JD Edwards app enables Access Gateway to SSO with JD Edwards applications. By default this application passes the JDE_SSO_UID header to the JD Edwards. See Add an Oracle JD Edwards application.

 

Supported versions:

  • v9 or later

Oracle PeopleSoft

PeopleSoft application

The PeopleSoft configuration enables Access Gateway to SSO with Oracle PeopleSoft applications. By default this application passes the PSUSER header to the PeopleSoft application. PeopleSoft must have been configured to enable SSO. Contact Oracle for assistance with PeopleSoft SSO configuration.
See Add an Oracle PeopleSoft app
Supported versions:

  • v9.2.00 or later.

Oracle WebCenter

Out of the box Access Gateway WebCenter application type

The Oracle WebCenter app enables Access Gateway to SSO with WebCenter applications. By default this application passes the OAM_REMOTE_USER header to the WebCenter. Contact Oracle for assistance with WebCenter SSO configuration.
See Add an Oracle WebCenter App .

Oracle WebLogic

Out of the box Access Gateway WebLogic application type

The Oracle WebLogic app enables Access Gateway to SSO with WebLogic applications. By default this application passes the OAM_REMOTE_USER header to the WebLogic. Contact Oracle for assistance with WebLogic SSO configuration.
See Add an Oracle WebLogic Server App

 

Supported versions:

  • v10.3.6 (11g) or later

Qlik

Qlik business analytics application

The Access Gateway Qlik configuration enables header-based SSO with Qlik. Consult the Access Gateway helpdesk article or your Qlik view document to enable header-based authentication. After Qlik is configured this Access Gateway application needs to be configured to pass the appropriately named header to Qlik for SSO.
See Add Qlik application.

 

Supported versions:

  • All

Salesforce

Salesforce

The Access Gateway Salesforce configuration enables SSO with Salesforce.

Wikipedia Protected

Wikipedia protected

The Access Gateway Wikipedia protected configuration enables Access Gateway to perform SSO with Wikipedia based applications.