Support Article
Authentication fails when invoking two Connectors sequentially
SA-92975
Summary
When two separate REST Connectors have two deferent Authentication Profiles with the same 'Client ID' (but with Deferent Token Endpoints), the application overrides the same OAuth2.0 token instance without creating two deferent token instances.
The Pega application must create two separate tokens when the end point is deferent even the Client ID is the same.
Error Messages
Not Applicable
Steps to Reproduce
- Create two REST Connector rules with deferent OAuth2.0 Authentication profiles.
- Ensure that the 'Client ID' and 'Client Secret' is the same for both the Authentication profiles and the Token Endpoint is Deferent (Deferent end points should generate two Deferent tokens).
- Call two Connector rules sequentially.
Root Cause
When the 'Client ID' and the 'Client Secret' are the same for both the Authentication profiles and the Token endpoint is deferent, then the Access token is overridden.
Resolution
Perform the following local-change:
Request for Deferent Client IDs or Scopes. The Authentication Provider or the Token Endpoint must be a key parameter for the Token instance.
Published December 2, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.