Block Secrets from Being Visable
Samuel Adams
Block Secret Org Variables from being displayed in the Web GUI or in the Rewst Workflow Results page. This would allow for the secrets to be visible for 1 time only, then it would be redacted. This would increase the security of those secrets.
Log In
Ethan Oscini
I think just doing the
*** REDACTED ***
thing that happens with other stuff would work in my opinion. I have to use HTTP requests for some things and despite making the API keys secret org vars, seeing them in plaintext in workflow logs makes me shudderChris Hansen
I see my suggestion was merged into here, but I don't think they're related and should not have been merged. My issue is that I want different forms for the same workflow to pass a hidden variable in the background that can't be modified by the form user. I said nothing about org variables, I need to pass a hidden field value into the workflow from the form.
What Sam is talking about is having actual secure org variables that can only be entered once and can never be seen again. This is standard practice in many places, and is an absolute necessity in a platform like this. I think this feature is also needed, but not related to my suggestion.
D
Danial Gagne
Merged in a post:
Hidden data fields for forms
Chris Hansen
I would like to see a feature to make "hidden" form fields that still pass their data into a workflow.
D
Danial Gagne
Merged in a post:
Ability to redact data from Triggers and Data Alias'
Brody Atto
Currently it is only possible to redact information generated from individual actions, but not from data alias' or from data passed in from a triggers. For example data passed into a field from a web hook will be fully visible in the history.