Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicit API key tokens #367

Closed
tsimbalar opened this issue Feb 19, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@tsimbalar
Copy link

commented Feb 19, 2016

Hi,

I've seen the blog post about remote Serilog level control and this sounds great !
But we have not used API keys so far in the applications we have deployed ... we will probably use it from now on, but thinking of the approach to do that, I thought it was maybe a bit tedious and there might be room from improvement.

To use API keys on many applications, If I understand correctly, the process currently :

  1. Go to_ Seq Settings_
  2. Declare an application
  3. Copy the api Token
  4. go paste it in the application's config file

-> Repeat N * M times , N being the number of things we deploy (a component of an app) and M being the number of environments we deploy to

I would love to see an approach where we just fill in some arbitrary string as a token in our app config files and map it to the Api Key afterwards.

The process would be :

  1. I prepare my config file filling in an arbitrary token (ideally, something sensible and human readable like MyApp.MyComponent-DeployEnvironment) this could be done during deployment.
  2. I deploy the app in its environment
  3. in Seq, somewhere I can see a list of Api Keys used by clients that have not yet been "officially registered in Seq"
  4. from there I can promote an item of this list to an "official registered" API Key, with all the goodies that apply (added properties, extra filter, level control)

The idea is that I can just register all those apps from one page instead of going back and forth between Seq and the config files.

It is my understanding that the api Key is not specially secret or anything, so the format does not have to be an obscure string.

Does this make sense ?

@nblumhardt

This comment has been minimized.

Copy link
Member

commented Feb 21, 2016

Thanks for the thoughtful post, some great ideas here.

@nblumhardt nblumhardt added this to the 3.4-pre milestone Aug 29, 2016

@nblumhardt

This comment has been minimized.

Copy link
Member

commented Sep 15, 2016

image

image

image

@nblumhardt nblumhardt closed this Sep 15, 2016

@nblumhardt nblumhardt changed the title API key declaration "a posteriori" Explicit API key tokens Sep 19, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.