It's therefore important that you make all of the necessary checks to verify the validity of your requests and the responses.
This section provides instructions on how to configure Azure AD with a single-page application (SPA) so that users can authenticate through it and make requests to the WorkflowGen GraphQL API. This configuration is done in three steps: registering your SPA, granting access to the API, and setting some redirect URLs.
Make sure to have a licensed copy of WorkflowGen installed and running on a server.
Make sure to have administrative access to Azure AD to be able to configure it properly.
Make sure to have provisioned an existing Azure AD user with which you can authenticate to WorkflowGen so that you can use the application afterwards.
Make sure to have successfully configured delegated authentication to Azure AD on your WorkflowGen instance following the instructions in the Azure Active Directory authentication section.
In the Azure portal, click App registrations in the Azure Active Directory section.
Click New registration, and fill in the properties:
Your SPA name
Supported account type:
Accounts in this organizational directory only
Note: Depending on the context, you should choose the right option for your use case for the supported account type.
https://<your SPA login url>
Click Register at the bottom of the page.
You should now be in your newly registered application's overview page.
Go to the Implicit Grant subsection in the Advanced settings section.
Check the Access tokens and ID tokens checkboxes.
Now that you've successfully registered your SPA, you need to grant it access to the WorkflowGen API, which should be already registered if you've met the prerequisites.
Click API permissions.
In the API permissions section, click Add a permission.
Click My APIs, then select the WorkflowGen Server application.
Click Delegated permissions, then select user_impersonation.
Click Add permissions.
You should now see the WorkflowGen server in the list of your registered SPA's API permissions. Therefore, when requesting an access token to Azure, based on the audience you should be able to obtain a correct token that you will send to your WorkflowGen instance's GraphQL API in addition to the request.