OAuth 2.0 and OpenID Setup

DEXPRO Core provides shared authentication setup for the DEXPRO apps that call external services. Two setup lists are available: one for OAuth 2.0 client-credentials connections and one for OpenID Connect connections. Both keep secrets in Business Central isolated storage so they are never shown again after entry.

Purpose

Several DEXPRO features connect to external services — for example the Freeze archive, the SQUEEZE tenant, Digivoice, and Microsoft Graph. These connections need to authenticate. Instead of each app defining its own credentials, Core stores the connection settings centrally and issues the tokens the apps need.

OAuth 2.0 Setup Entries

The OAuth 2.0 Setup Entries page holds client-credentials connections. Each entry defines how Core obtains a token for a given service.

• Service URL — the base URL of the service to call.
• Token Path — the endpoint used to request an access token.
• Client ID — the application (client) identifier.
• Tenant ID — the tenant the token is requested for.
• Scope — the scope requested for the token.
• Client Secret — entered through a dedicated dialog and stored in isolated storage.

{add screenshot of OAuth 2.0 Setup Entries here}

OpenID Setup Entries

The OpenID Setup Entries page holds OpenID Connect connections.

• OpenID endpoints — the OpenID Connect endpoint(s) used for authentication.
• Client ID — the application (client) identifier.
• Grant Type — the OAuth grant type used.
• Scope — the scope requested.
• Secret and token — stored in isolated storage.

{add screenshot of OpenID Setup Entries here}

Entering a secret

Secrets are entered through a dialog and written straight to isolated storage. They are used when Core requests tokens on behalf of the apps.

For security, secrets are never displayed again after they are entered. If a secret changes, re-enter it through the dialog — you cannot read the stored value back from the page.

Prerequisites

• The service you are connecting to must be registered and must provide the client ID, tenant ID (where applicable), scope, secret, and endpoint values.
• For Microsoft Graph connections you need a Microsoft Entra ID app registration (see "File Viewer" and "File Viewer Setup Wizard").

Related features

• File Viewer
• File Viewer Setup Wizard
• Extensibility