Mark Connector header field as secret

Product Suggestions
1

Hi Tulip Community,

I’m working with a Connector that requires passing an API key as part of the Request Headers. Unfortunately, this results in the API key being displayed as plaintext in any created Function.

It would be nice if there were a way to mark specific headers as secrets so they could be masked in the UI. (I wasn’t able to find a way to do this—please let me know if this already exists!)

Thanks!

2

Thanks for posting Michael.

Wanted to get you a quick response — we’ll pass this along to the right Product team internally and circle back next week.

To add to what we pass along, are you hoping that select headers are masked on display in the Connectors Environment Settings, on Export/Import, or somewhere else?

  • Olga
3

Hey @mjs -

Thanks for this feedback - this is something I have had in the back of my mind for the last few years, but had never surfaced in a customer ask (that I am aware of). I have created a ticket to track this.

The pattern of auth being stored to headers is a common one (especially for custom x-auth setups) and the ability to hide these fields would be beneficial from the UI, to logs, to Import and Export.

Thanks again for the suggestion-
Pete

1 Like