Skip to main content

How to store sensitive API keys that the user has entered?

  • August 13, 2020
  • 3 replies
  • 46 views

Andy_Cloke
Forum|alt.badge.img+17

Based on the advise here, I’m going to ask the user to enter an license/API key in order to prove they have subscription. My block might also need to store sensitive keys for other APIs.

Where should I store these sensitive keys?

This guide says it shouldn’t go in GlobalConfig.

This answer says it should be an environment variable, but I want to enable non techincal users to install my block, so that doesnt feel like an option.

3 replies

Andy_Cloke
Forum|alt.badge.img+17
  • Author
  • Known Participant
  • 91 replies
  • August 13, 2020

I’m assuming - we need to implement a full login screen to authenticate the user, and protect any keys behind that


  • Participating Frequently
  • 7 replies
  • August 20, 2020

I’m assuming - we need to implement a full login screen to authenticate the user, and protect any keys behind that


I am actually coming across the same issue. I would like a place to store API keys as for our service we can’t do something like set up passport.js to run third party authentication as we don’t pay for enterprise level.

Not sure if passport.js will help you out though if you can log into the service you are using with third party authentication it should work.

Any chance the Airtable team have added a place to store .env info and I have just missed it?


Forum|alt.badge.img
  • New Participant
  • 2 replies
  • December 22, 2022

 Hey Andy,

what did you end up using to store API keys?