Skip to Content

Configure authentication for an offline app in Jitterbit App Builder

Introduction

Authentication for an [offline app(/app-builder/how-to/offline-app/) requires configuration steps in both the core app and the offline app. This page describes these, and how to test them.

Core app

When a user logs into an offline app, they are authorized and given permissions via the associated core app. To allow this, you must configure the following in the core app:

Security provider group

You should create a security provider group in your development environment, then propagate it to your QA or production environments using the usual [application package management(/app-builder/how-to/build-release/) method.

To create a security provider group, follow these steps:

  1. Open your core app for editing.

  2. Select App Workbench from the action drawer, or Workbench from the application menu, then click Roles.

  3. Click the Application Groups button to open the Group and Roles dialog.

  4. Under Group, click the Create button.

  5. Enter a name (for example Offline App Security Provider) and description for the group, then click the icon to save it.

  6. Close the dialog.

Tip

Permissions are not provided by this group, but by the association of the group with the security provider, done in the next section.

Authorization security provider

The authorization security provider enables [OpenID authentication(/app-builder/documentation/security/providers/openid-connect/) for the offline app. It must be configured in any environment that the offline app might authenticate with.

To configure an authorization security provider, follow these steps:

  1. Select IDE > Security Providers.

  2. In the User Authentication table, click the icon at the end of the Authorization Server row to open the record.

  3. Under Provider, click the Edit button, then make any required changes.

  4. When the provider is configured, click Enabled to enable it, then click the Save button.

  5. Under Provider, select More > Manage Groups.

  6. In the Groups dialog, click the Create button.

  7. In the Provider Group dialog, set the following values:

    • Name: Offline App Security Provider

    • Identifier: Offline App Security Provider

    • Group: Click to open the menu, then select the Offline App Security Provider group.

  8. Close the Provider Group dialog, then close the Groups dialog.

Tip

The security group identifier (Offline App Security Provider in this example) is used later to configure the offline app security provider.

Client

To create a client, follow these steps:

  1. Select IDE > User Management.

  2. Select the Clients tab.

  3. Click the + Client button.

  4. In the dialog, set values for the following under Client:

    • Name: Offline App Client

    • Description: Enter a description.

  5. Click the Save button.

  6. Under Redirects, click the + URL button.

  7. Enter the following in the field, then click the icon to save it:

    https://localhost:5001/signin-OpenID

    • localhost: This is a literal string; you do not need to substitute a hostname or IP address.

    • OpenID: This part of the URL can be different but must match exactly the name of the OpenID security provider (set later).

  8. Under Client, select More > Advanced.

  9. In the Advanced Settings dialog, click to enable both Require PKCE and Public, then close the dialog.

  10. Copy or note the Client ID for later use, then close the dialog.

Offline app

To configure the offline app, you must do the following:

User groups

As with any App Builder app, you should create [user groups(/app-builder/documentation/security/users-groups/) for the different types of user expected to use the app, or at least the following:

  • A User group, for general users of the app.

  • An Administrator group, for developers and administrators.

OpenID security provider

You need a security provider to test authentication on development (off-device) instances of your offline app. This security provider information can be exported as a JSON file and used to automatically set up the provider on mobile devices. Jitterbit support uses the JSON file when creating builds of the offline app for your mobile devices.

To set up an OpenID security provider, follow these steps:

  1. Select IDE > Security Providers.

  2. Under User Authentication, click the + User Authentication button.

  3. Under Provider, set the following values:

    • Settings

      • Name: OpenID

        Important

        This value must match exactly the client redirection URL suffix (set previously) in the core app.

      • Type: Vinyl / OpenID Connect

      • Priority: (Default).

      • Enabled: Enabled.

    • Tokens

      • Owner: User (default).

    • Sign In

      • Redirect On Challenge: Disabled (default).

      • Show On Login Form: Enabled.

      • Default Page: Blank (default).

      • Sign Out Page: Blank (default).

    • Provisioning

      • User Provisioning: Enabled.

      • Match Existing User: Enabled.

      • Supplies Group Membership: Enabled.

      • Name Format: Blank (default).

      • Name Identifier Format: Blank (default).

      • Identity Provider URL: Blank (default).

  4. Click the Save button to save the provider.

  5. Under Endpoints, click the + Endpoint button.

  6. In the Endpoint dialog, set the following:

    • Endpoint Type: Click to open the menu, then select OpenID Connect Issuer.

    • URL: Enter the URL of the core app App Builder server that the offline app authenticates with.

  7. Click the Save button, then close the Endpoint dialog.

  8. Under Credentials, click the + Credential button.

  9. In the Credential dialog, set the following:

    • Type: Click to open the menu, then select Client.

    • User Name: Enter the Client ID (noted previously).

  10. Click the Save button, then close the Credential dialog.

  11. Under Properties, click the + Property button.

  12. In the Properties dialog, set the following:

    • Parameter: Click to open the menu, then select Scopes.

    • Value: openid profile email phone api groups

  13. Click the Save button, then close the Properties dialog.

Group association

The offline app is granted access via the OpenID security provider group identifier set up on the core app App Builder instance.

To associate the group with the provider, follow these steps:

  1. Select IDE > Security Providers.

  2. In the User Authentication table, click the icon at the end of the OpenID row to open the record.

  3. Under Provider, select More > Manage Groups.

  4. In the Groups dialog, click the Create button.

  5. In the Provider Group dialog, set the following values:

    • Name: Enter a name of your choice.

    • Identifier: Offline App Security Provider

    • Group: Click to open the menu, then select the Offline App Security Provider group.

  6. Click the Save button, then close the Provider Group and Groups dialogs.

Connector data sources

Any offline app App Builder connector data sources that access the core app must use the OpenID security provider just created.

For all such connectors, do the following:

  1. Select IDE > Data Servers.

  2. In the Data Servers table, click the Details button for the data source.

  3. In the Server dialog, ensure the URL is your core app App Builder instance, then click the Edit button.

  4. Expand the Security Settings group.

  5. Click to open the Security Provider menu, then select OpenID (the security provider created previously).

  6. Click the Save button, then close the Server dialog.

Test

When configuration is complete, a button Sign in with OpenID appears on the offline app's App Builder login screen.

The following is an example of a simple test pattern:

  1. On the core app App Builder instance, create a local user with a password.

  2. On the offline app App Builder instance, log in with this user.

  3. Verify access to your offline app, and check the functionality of any pages that use App Builder connectors.