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

Ensure secured API key param restrictSources only accepts string #578

Open
aseure opened this issue Mar 12, 2020 · 0 comments
Open

Ensure secured API key param restrictSources only accepts string #578

aseure opened this issue Mar 12, 2020 · 0 comments

Comments

@aseure
Copy link

aseure commented Mar 12, 2020

When generating secured API keys, an optional restrictSources
parameter can be used as a string (such as "192.168.1.0" or
"192.168.1.0/24"). We discovered that some API clients wrongly accept other
types (such a list of strings, etc.) which is wrong.

Could you make sure that restrictSources only accepts string as a valid type
as a secured API keys parameter?

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

No branches or pull requests

1 participant