Creating Ensign API keys
Now it’s time to provision read and write access to our Ensign topics.
We can create new Ensign API keys to enable users or applications to publish new data to our project topics, or to subscribe to the topics.
Since I’m the maintainer of this project, I’m going to give myself full read-write access.Your keys have two parts - the client secret and the client id. You’ll need both of these to open a client connection to Ensign
Remember to download your keys and save this file!
I like to rename my file after the project so I don’t forget later.
You can add the client id and client secret to your environment variables, or you can put the file into your Git repository, as long as you gitignore it!
Remember not to share your keys with anyone, and never commit them to a public GitHub repository
If your keys get lost or compromised, don’t panic. Revoke them and create new ones.
API keys are defined at the project level, and everyone collaborating on the datasets will need their own API keys.
Once you add teammates to your project, they can create their own API keys using the same technique.