Secret Not being redacted

Data Actions
1

I'm setting up a new Web Services integration, which works perfectly.
But when expanding the steps when testing the Auth data action, the client Id is redacted but the secret is not.
If anything I want the secret to be redacted

Secret and Id are provided in the body, not headers.
Content type is application/x-www-form-urlencoded if that matters

I setup the variables as part of the integration setup, so not hard coding them.
clientId
clientSecret

And again the authentication works. And clientId is redacted, along with the token etc as expected, but clientSecret is not redacted on the Data Action test in the UI on step 7 Resolve request body template.

Is there a way to ensure this gets redacted?

2

I just did a test of this and the secret that I used was properly redacted. The only reason I know that this would happen is that we don't attempt to redact credential information that is 1 or 2 characters long. If that is not the cause of what you are seeing please open up a support case ASAP so we can dig further into this.

--Jason

3

Hi Jason,

Thanks, I managed to get the values in to and accepted in an Authorization header which gets redacted.
But was certainly a standard client secret, like the one Genesys generates in oauth creation.

4

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.