Static Key(s) as array?

[corepay]

Hello thank you - this saved my hours and errors

Couple questions...

1. Can I use this for multiple header api keys? For example, I have an x-api-key for my applications service...would like to also have an x-developer-key that checks my developers service.

2. extending question 1... Can I also use the 'static' set api-key method in addition to the lookup method? If so, can you make this an array lookup? For example, I have several server to server connections and I want to provide those an x-server-key header option.

IRL scenario if this helps:

• I am trying to put together platform backend services where developers can build applications using a REST API. These developers register, system creates and issues a key for each developer I want them to put in header as x-developer-key
• The developer creates apps in my application service, system creates a key for each application I want to them to put in the header as x-api-key
• I communicate between servers inside and outside firewall. I want to manually provide an x-server-key header value and put it in an array of keys that is evaluated using the static method.

Again, thank you for your time here and sharing.

[corepay]

Hi, yes I got it working, simple actually no changes other than putting in missing the key-names into the authstrategy object. My bad...but this is real good.

So - all that's left is it possible for you to do an update allowing an array of keys in static?

[TheSinding]

Is there any reason, you can't set it up with the service method?
Just add a field in the service, which indicates whether or not it is a developer key?

[corepay]

Is there any reason, you can't set it up with the service method?
Just add a field in the service, which indicates whether or not it is a developer key?

Hello, back on this...

To answer your question - I want to use the static key as an array for system administrators. they get issued their own 'x-master-key' that is stored in an array - these admins may or may not be setup as users key bypasses all jwt user login authentication in addition to some required relationships I have when creating or querying users.