Developer Deep Dive: Live Experience Authentication

The first step in integrating Oracle Live Experience into your app is gaining access to the service.

Live Experience SDK uses a JSON Web Token (JWT) as the access key. It's up to the developer to request a JWT and keep it up to date.

A REST call is used to retrieve a JWT access token. See the Oracle Live Experience REST API Reference for more information.

While this REST call can be made from your app directly, it requires your tenant's authentication (client_id/client_secret) credentials. If these credentials change, you'll need to update the app on all devices it has been deployed to. A better approach is to have a web application make the REST call on the device's behalf. This gives you a central point of control and allows integration with an existing enterprise authentication or SSO platform.

For an example implementation of centralized authentication in iOS, see Authenticate with Live Experience for iOS.

See the following for more details about the JWT access token, waiting for authentication, how to handle JWT expiration, and steps to troubleshoot authentication problems in your application:

• The JWT Access Token
• Waiting for Authentication
• Handling Access Token Expiration
• Authentication Troubleshooting