Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Ram Reddy Bitla (Ram Reddy Bitla)
Swedbank
Ram Reddy Bitla
Swedbank
SE
Ram Reddy Bitla Member since 2013 4 posts
Swedbank
Posted: Feb 13, 2019
Last activity: Mar 20, 2019
Posted: 13 Feb 2019 7:56 EST
Last activity: 20 Mar 2019 17:51 EDT
Closed

Request for Connect-Rest is getting changed by pega

Hi.

I am configuring a connect-Rest to integrate with the external service (Mitek). where i need to pass client id and secret id as params to get the Auth token. secret id contains special characters (^) in the log file i can see ^ is replaced with %5E because of which Invalid client error is thrown.

Can anyone please suggest? is this an expected behavior and how to resolve this please>

***Edited by Moderator: Pallavi to update platform capability tags***

To see attachments, please log in.
Low-Code App Development
Data Integration

Posted: 6 years ago
Posted: 20 Mar 2019 17:51 EDT
Paul Gentile (PaulGentile_GCS)
PEGA
Principal Engineer, Technical Support, 1:1 Customer Engagement
Pegasystems Inc.
US

You're not going to see an unencrypted key in the log file. I'm surprised you're seeing anything other than "********". Is this an OAuth2 token? If so, you won't see that logged for security reasons.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice