Walkthrough — Google OpenID connection with Appian 23.1+
The purpose of this guide is to walk through step-by-step how to configure Google OpenID with Appian 23.1
Steps are as follows:
- Log into the Google Console https://console.cloud.google.com/apis/credentials
- Click on Projects and create a “New Project”
3. Give the project a name and click “CREATE”
4. Now, configure the consent screen by clicking on the right button “CONFIGURE CONSENT SCREEN”
5. Once created, the following information are required:
Click “SAVE AND CONTINUE” until completed.
6. Create the Client ID/Secret from clicking the “Credentials”
7. Click on “+CREATE CREDENTIALS” and select “OAuth client ID”
8. From the Application type drop-down select “Web Application” and in the name field provide any recognizable name. Click on “+ADD URI” and add the callback URI from the Appian Console / Authentication / Openid Connect Page.
9. Click “CREATE” and the ClientID/Secret will be displayed and also have the option to download the json file
10. Click “OK” and then access the OAuth 2.0 Client Id
Now, move to the Appian 23.1 Admin Console and create a new OpenID Connection with the following information:
ClientID/Secret
Discovery Endpoint URI: https://accounts.google.com/.well-known/openid-configuration
Scope: openid email profile
Username Claim: email
Authentication Group: OIDC (Create a new one)
11. Click on “VERIFY MY ACCESS”
12. To create users during the authentication process in Appian, enable “Attribute Mapping” and add the following claims:
13. Edit the Authentication Group “OIDC” and add a membership rule to include ALL users to this group when authenticating.
14. Now test the authentication flow as follows:
Access https://<appianSite/suite
Choose the account to authenticate
Logged into Appian
Additional Information:
Walkthrough — Azure OpenID connection with Appian 23.1
https://tony-marziano.medium.com/walkthrough-azure-openid-connection-with-appian-23-1-f4167f2a2c8b
Disclaimer:
The content of this article is purely my work and efforts and is not endorsed nor regarded as official documentation by Appian.
