As of WorkflowGen Plus version 1.2.0 and WorkflowGen server version 7.11.2, you can generate a universal link to simplify the login process for your WorkflowGen Plus mobile app users. Once you’ve generated the universal link, give it to your users, who can use it to sign into WorkflowGen Plus with the preset sign-in method.
For instructions on how to log in using Azure AD, AD FS 2016, Auth0, Okta, or classic methods, see the WorkflowGen Plus v1 sign-in and authentication topic.
Base URLs
The protocol and hostname base URLs are common to all authentication methods:
| Parameter | Value |
|---|---|
protocol |
workflowgenplus:// |
hostname |
auth.init |
Azure AD parameters
| Parameter | Value |
|---|---|
provider |
azure-v1 |
tenant_id |
Use the tenant ID you created in the Azure AD configuration (e.g. 4b72dd6c-013e-4a9c-b837-f03a58cb8fd1) |
client_id |
Use the client ID you created in the Azure AD configuration (e.g. 6g909d00-8580-49a4-9003-a30f6b87ae86) |
audience |
Your WorkflowGen web application URL (e.g. http://workflow.mycompany.com/wfgen)Note: This value must be URL encoded. |
The universal link should follow this format:
workflowgenplus://auth.init?provider=azure-v1&tenant_id=6g909d00-8580-49a4-9003-a30f6b87ae86&client_id=4b72dd6c-013e-4a9c-b837-f03a58cb8fd1&audience=http%3A%2F%2Fworkflow.mycompany.com%2Fwfgen
AD FS 2016 parameters
| Parameter | Value |
|---|---|
provider |
adfs |
client_id |
Use the client ID you created in the AD FS 2016 configuration (e.g. 6g909d00-8580-49a4-9003-a30f6b87ae86) |
domain |
The AD FS domain name without the URL protocol (e.g. mycompany.com) |
audience |
Your WorkflowGen web application URL (e.g. http://workflow.mycompany.com/wfgen).Note: This value must be URL encoded. |
The universal link should follow this format:
workflowgenplus://auth.init?provider=adfs&client_id=6g909d00-8580-49a4-9003-a30f6b87ae86&domain=mycompany.com&audience=http%3A%2F%2Fworkflow.mycompany.com%2Fwfgen
Auth0 parameters
| Parameter | Value |
|---|---|
provider |
auth0 |
client_id |
Use the client ID you created in the Auth0 configuration (e.g. 7gdj4hs92y) |
domain |
The Auth0 domain name without the URL protocol (e.g mydomain.auth0.com) |
audience |
Your WorkflowGen GraphQL API URL (e.g. http://workflow.mycompany.com/wfgen/graphql).Note: This value must be URL encoded. |
The universal link should follow this format:
workflowgenplus://auth.init?provider=auth0&client_id=7gdj4hs92y&domain=mydomain.auth0.com&audience=http%3A%2F%2Fworkflow.mycompany.com%2Fwfgen%2Fgraphql
Okta parameters
| Parameter | Value |
|---|---|
provider |
okta |
client_id |
Use the client ID you created in the Okta configuration (e.g. 0o7gdj4hs92yh7) |
domain |
The Okta domain name without the URL protocol (e.g. https://dev-958754.oktapreview.com/oauth2/{AUTH_SERVER_ID}/.well-known/openid-configuration)Note: This value must be URL encoded. |
audience |
Your WorkflowGen web application URL (e.g. http://workflow.mycompany.com/wfgen)Note: The value must be URL encoded. |
The universal link should follow this format:
workflowgenplus://auth.init?provider=okta&client_id=0o7gdj4hs92yh7&domain=https%3A%2F%2Fdev-958754.oktapreview.com%2Foauth2%2F{AUTH_SERVER_ID}%2F.well-known%2Fopenid-configuration&audience=http%3A%2F%2Fworkflow.mycompany.com%2Fwfgen
Classic authentication parameters
Parameters
| Parameter | Value |
|---|---|
provider |
basic |
audience |
Your WorkflowGen web application URL (e.g. http://workflow.mycompany.com/wfgen)Note: This value must be URL encoded. |
username (optional) |
The username (e.g. charles) |
The universal link should follow this format:
workflowgenplus://auth.init?provider=basic&audience=http%3A%2F%2Fworkflow.mycompany.com%2Fwfgen&username=charles