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
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?
The text was updated successfully, but these errors were encountered:
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 othertypes (such a list of strings, etc.) which is wrong.
Could you make sure that
restrictSources
only accepts string as a valid typeas a secured API keys parameter?
The text was updated successfully, but these errors were encountered: