Configuring OpenID Connect confidential client in AD FS - HxGN EAM - 12.0.1 - Feature Briefs - Hexagon

HxGN EAM OpenID Connect

Search by Category
Feature Briefs
HxGN EAM Version

The images and the configuration details in this section are from AD FS Management version installed on Windows Server 2019.

Configure an OpenID Connect client.

  1. Open the AD FS Management application.

  2. Right-click the Application Groups, and then select the Add Application Group option from the menu.

  3. In the Add Application Group Wizard, provide the Name and Description of the OpenID Connect Client, and then select the Server application accessing a web API.

  4. Click Next.


  5. On the Server Application screen, a Client Identifier will be automatically generated. Copy this value and store it separately as it will be required while configuring OpenID Connect in the EAM Application. On the same page, a Redirect URI should be added. This will be the URI to which the authentication request will be redirected to along with an authorization code in the authorization code grant flow of OpenID Connect.

    The Redirect URI referenced in the screenshot is only for demonstration and should not be used in the actual setup of the OIDC client.


  6. On the Configure Application Credentials screen, select the Generate a shared secret checkbox. This will generate a secret. Click the copy to clipboard button and store it separately. This will be the Client Secret.


  7. On the Configure Web API screen, copy the Client Identifier generated in the previous step and add it as the Identifier.


  8. On the next screen, select the default access policy, Permit Everyone.

  9. On the Configure Application Permissions screen, select allatclaims and openid in Permitted scopes.


  10. Click Next to navigate to the Summary screen.


  11. Click Next to complete the wizard.