Issue in Masking Sensitive Data in Apigee debug trace

[ahitankar]

Hi Team,

I am attempting to mask sensitive data in the response using the Apigee Management API. Below is the Management API endpoint we are working with. However, in the debug session for the API where the data needs to be masked, the masking does not seem to occur for GET requests, though it works for POST requests. Could you provide some assistance with this issue? Interestingly, when a GET request is made after a POST request has been made for the same API, the data gets masked. Does the configuration require that a POST request be made first to ensure the data is masked? How to overcome this scenario? Because my all request endpoints are GET not POST.  

Thank you.

[AlexET]

Hi there @ahitankar, thank you for posting your question in the Apigee forum.

It appears the community hasn't yet shared any suggestions. We're currently looking into it, thank you for your patience and participation.

[jadelgado]

Hello @ahitankar ,

I would recommend reviewing the following points:

• Check if the JSON response is exactly the same for both GET and POST methods. Since fields within JSON are case-sensitive, the case must match exactly for a JSON field to be masked.
• Ensure that the debug session is started in the environment configured to mask the data.
• If you would like to mask data from the request, you could use requestJSONPaths field as well. 
• If you change your data masking configuration, you must start a new debug session to see the effect of your change. 

Please refer to the Masking and hiding data documentation for further details. 

Let us know if any other questions arise. 

Thank you!