Problem Statement Currently, when configuring Web APIs that use OAuth 2.0 Client Credentials authentication, the Token URL (Authorization URI) endpoint cannot be configured using a variable. While other settings, such as the Base URL, support the use of variables, the Token URL requires a static value. Although it was indicated that this functionality works in version 7.2, testing has shown that the same limitation still exists as in NextGen. Attempts to use a variable for the Authorization URI result in validation or runtime errors. Business Impact Increases administration effort when maintaining multiple environments (DEV, TEST, ACC, PROD). Reduces reusability and portability of objects between environments. Requires manual updates to authentication endpoints after deployment. Creates inconsistencies, as variables are supported for other endpoint configurations but not for the Token URL. Limits organizations that frequently change identity providers, endpoints, or tenant-specific authentication URLs. Requested Enhancement Allow the Token URL / Authorization URI used for OAuth 2.0 Client Credentials authentication to be configured through an environment variable, in the same manner as Base URLs and other endpoint settings. Expected Benefits Simplified environment management. Improved deployment automation. Reduced configuration errors. Greater consistency across Web API configuration settings. Better support for CI/CD and multi-environment implementations. Current Workaround Administrators must manually update the Token URL for each environment or maintain separate configurations, which increases operational overhead and risk.
... View more