This page provides detailed information about how Appian uses an existing OpenID Connect (OIDC) configuration to authenticate requests for an HTTP connected system. Appian developers can use this authentication type to give users seamless access to external resources through integration calls.
There are two steps you must complete before can use OIDC for authentication:
Once you've completed the prerequisites, you can select OpenID Connect as the authentication mechanism for your HTTP connected system.
To verify that you can call an integration using your environment's OpenID Connect configuration, click Inspect Tokens. This will check the status of your access and refresh tokens against the OIDC provider. Since the same provider is used for any user authenticated and authorized by OIDC, you only need to test your account to ensure that the connection is established.
You will see one of a few possible messages depending on the result of the inspection.
If your tokens are valid and working as expected, you'll see the following message:
Both an access token and refresh token were found for the OpenID Connect provider.
If Appian locates an access token for your user but has no refresh token, you'll see the following warning:
An access token was found for the OpenID Connect provider, but no refresh token was returned.
If there is a problem with your tokens, the following error message is shown:
Neither an access token nor a refresh token was found for the OpenID Connect provider.
If an access token, refresh token, or both cannot be found, the OpenID Connect configuration may need to be updated by an administrator.
If a user can sign in using OIDC, but they are unable call an integration built on an HTTP connected system using OIDC, check that they are in the OpenID Connect Integration Users system group.
OpenID Connect Authentication