Sanitize Run History Content
Many authentication method used to connect to 3rd party system, cannot be passed as part of Authentication Header.
Need a feature so that we can sanitize the content of Run History as required, so that all the developers/operation folks don't have access to credentials in plain text.
Eric Willman commented
Is this still in the works?
Olof Ottensten commented
I would also like the status for this.
Currently everything is logged (even if you get a secret from a KeyVault) .
We REALLY need a way to obfuscate certain output from the Logic App log!
Has this being implemented? How people is dealing with this right now?
Tom Schulte (Plex Systems) commented
I need this too but voted instead on https://feedback.azure.com/forums/287593-logic-apps/suggestions/17116240-authentication-information-visible-for-a-logic-app which seems to describe the same feature
Frederik Gheysels commented
This is something that could indeed be very helpfull.
Suppose a Logic App that calls a Web API / Service App; one of t he parameters of the POST request is something that should not be in plain text when the runhistory of the logic-app is inspected.
How can it be done ? I've been trying to modify the swagger definition of the API (specify the formatt = 'password' for that property in the swagger definition) but to no avail.
I know it is done for the password property that is sent to the authentication header, but is it also possible to enable that for other things as well ?