Integrated Services¶
Integrated Services defines external OpenAuth-backed services that Emakin can use for capabilities such as sign-in, single sign-on, and access to related external resources.
When to Use This Page¶
Use this page when you need to:
- register an OpenAuth provider such as Google or Office 365
- configure client credentials and callback behavior
- define scopes for the provider
- configure service-account credentials for background or elevated access
Basic Service Definition¶
Each integrated service can define the following settings.
Is Enabled?¶
Controls whether the service is active. Disabling the service also disables related dependent features such as its login integration.
Service Type¶
Defines the provider type, such as Google, Office 365, Keycloak, or another supported OpenAuth service.
Name¶
Internal service identifier used by Emakin. This is not intended as an end-user display name.
Client Id¶
The client identifier issued by the provider.
Client Secret¶
The client secret issued by the provider.
Service Callback¶
Defines how the redirect URI is generated.
- Application Callback: uses a generic callback under the application name
- Domain Callback: uses the active domain address as the callback base
Scopes¶
Defines the scopes requested from the external service.
Service Authentication¶
By default, integrated services authenticate with Client Id and Client Secret. For privileged or unattended access, service-account settings can also be configured.
Service Account Id¶
Identifier of the service account.
Service Account Key Type¶
Defines how the service account key is provided:
FilePathBase64Json
Service Account Key¶
Stores the actual key value in the configured format.
The existing documentation includes a full JSON example for this setting and that example should be preserved when the page is edited further because it is operationally useful.