Overview

The Resource Server tab in the Okta applications page supports Cross App Access for applications that validate Cross App Access ID-JAG tokens and mint access tokens. If a software as a service application does not explicitly support Cross App Access, transactions with that application fail after Resource Server configuration. Verify application compatibility before enabling this feature to prevent transaction failures.

Applies To

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Cross App Access
• Resource Server tab
• Applications that validate Cross App Access ID-JAG tokens
• Applications that mint access tokens
• Software as a Service (SaaS) applications

Solution

What is the purpose of the Resource Server tab in Okta?

The Resource Server tab appears on the applications page in the Okta Admin Console. This tab enables Cross App Access for applications that validate Cross App Access ID-JAG tokens and mint access tokens. The Resource Server tab functions only for SaaS applications that explicitly support Cross App Access as a resource.

Unsupported Cross App Access configurations cause transaction failures

Transactions fail if a SaaS application lacks Cross App Access support after Resource Server configuration. Verify Cross App Access support directly with the SaaS application provider before configuring the Resource Server tab in Okta.

Related References

• Configure resource server connectors