EDG as an OAuth API client
Some EDG features require access to external APIs that are protected with OAuth. The external API may be another EDG instance that is configured with OAuth Authentication. This page describes how to configure EDG so that it can act as an OAuth client in these scenarios.
Configuring EDG as an OAuth API client
Note
When configuring this method of authentication, it is helpful to have a technical resource familiar with the OAuth 2.0 Authorization Server to assist with the configuration. TopQuadrant is unable to assist with specific configuration options for each customer’s Authorization Server.
Using EDG as an OAuth 2.0 client is configured through EDG Server Administration. Browse to your EDG webapp UI, and navigate to the OAuth Parameters Section of the System Configuration Parameters Admin Page.
The Token Request URL, Client ID, Client Secret, and Scope depend on the Authorization Server. See the Authorization Server examples below.
The Relying party identifier is a URL that identifies the resource being accessed. When EDG makes external API requests to a URL, and the URL starts with this Relying party identifier, then EDG will attempt authentication with this OAuth configuration. For example, if the resource being accessed is another EDG instance:
https://your.edg.server/edg/tbl/