| title | Add an app for Access Gateway offline mode | |||||
|---|---|---|---|---|---|---|
| meta |
|
|||||
| layout | Guides |
This guide explains how to create an app for use with Access Gateway offline mode.
Note: The Access Gateway APIs used in this guide are available in a Limited Early Access program and may be updated or changed based on feedback.
- Offline mode configured for Access Gateway. See Configure offline mode for Access Gateway.
- An identity provider (IdP) in your Access Gateway instance with failover mode set to
AUTOMATIC.
By default, apps behind Access Gateway require a connection to Okta to authenticate users. If Okta is unreachable, authentication fails and users can't access the app.
Offline mode apps are configured with a local directory as a fallback authentication source. When Access Gateway detects that Okta is unavailable, it switches to offline mode and authenticates users against the local directory instead. From the user's perspective, the sign-in flow looks the same regardless of whether Okta is reachable.
Offline mode apps require you to configure the authentication service and directory sync before you create the app. See Configure offline mode for Access Gateway.