search

revk / NOTSCO

One Touch Switching test system
Other
8 stars 1 forks source link

API Keys instead of OAUTH2 as an option ? #10

Closed rmills9 closed 2 months ago

rmills9 commented 2 months ago

Any way of adding API Keys as a way of auth for the simulator rather than OAUTH2 ?

Sample Format: POST /post HTTP/1.1 https://{fqdn}/letterbox/{version} apikey:

revk commented 2 months ago

Ok my concern is the API key has a load of baggage I think, something about signed stuff.

I could easily do a fixed configured apikey value each way if that makes sense?

But yes, happy to explore options.

rmills9 commented 2 months ago

Yeah sure. Sounds good

revk commented 2 months ago

Ok leave with me - I suspect to the test system the API key will be the same as the client secret and same the other way, i.e. if no client ID we do API key each way.

Does that make sense?

rmills9 commented 2 months ago

Yeah brill. Thanks appreciate it.

revk commented 2 months ago

OK maybe tomorrow. Are you in a position to test with it?

rmills9 commented 2 months ago

Yeah no worries. Yeah all ready to go. :)

revk commented 2 months ago

OK tomorrow, and should pre pretty easy to do.

Sorry, I should be like TOTSCO and say you need to book a slot in 8 weeks for that, LOL!

rmills9 commented 2 months ago

Wicked. hahaha yeah bit stupid the way they're doing it tbh.

revk commented 2 months ago

I'll re-read the TOTSCO specs on API keys, and see what I can do this morning.

revk commented 2 months ago

OK try that, leave client ID blank and put the APIKEY in the secret.