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

[Feature Request] Support for setting an API key included in all requests made to the server #151

Open
kyle-cackett opened this issue Nov 18, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@kyle-cackett
Copy link

Add support for setting an API key that would be included in the "X-APIkey" header in every request sent to the server. This would allow users to add another layer of security to their backends by rejecting requests that do not include their private API key as described in this stackoverflow post.

The use-case is that many people protect backend services using an authentication framework but it's usually necessary to bypass this authentication for any mobile apps that require access to an API since it's not possible to go through the browser-based authentication flow within the app. These "naked endpoints" are protected only by the backend application's built-in authentication which is likely not as hardened as the dedicated auth framework.

@kyle-cackett kyle-cackett added the enhancement New feature or request label Nov 18, 2022
@kyle-cackett kyle-cackett changed the title Support for setting an API key included in all requests made to the server [Feature Request] Support for setting an API key included in all requests made to the server Nov 18, 2022
@austinried
Copy link
Owner

This seems a little bit out of scope for a client, but I can see the use case for it, especially in a self-hosted environment. I would probably want the implementation to be a little more generic though, with just allowing any number of custom headers to be set for a server, with user-defined header names/values.

I'm not sure if this will make it into the initial 2.0.0 release but it's something I could see adding support for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants