You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In some projects, we are using API keys for authentication and I would like to be able to use it the same way as the pre-configured OAuth 2.0 authentication, for example.
Describe the solution you'd like
I‘d appreciate being able to create a new „authentication“ in the corresponding settings with type „API Key“.
Configuration options should be:
Where to put the API key in the requests (headers or query parameters)
Which parameter name to use for the header or query parameter, e.g., ˋapiKeyˋ or ˋOcp-Apim-Subscription-Keyˋ
Which value to use as the API key
Describe alternatives you've considered
Currently, I leave the authentication set to „No Auth“ and directly configure the header or query parameter in the REST endpoint configuration.
This works but feels a bit inconsistent given how the other authentication mechanisms can be configured, also as other API clients support API key authentication as a similar mechanism as well.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In some projects, we are using API keys for authentication and I would like to be able to use it the same way as the pre-configured OAuth 2.0 authentication, for example.
Describe the solution you'd like
I‘d appreciate being able to create a new „authentication“ in the corresponding settings with type „API Key“.
Configuration options should be:
Describe alternatives you've considered
Currently, I leave the authentication set to „No Auth“ and directly configure the header or query parameter in the REST endpoint configuration.
This works but feels a bit inconsistent given how the other authentication mechanisms can be configured, also as other API clients support API key authentication as a similar mechanism as well.
The text was updated successfully, but these errors were encountered: