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
In the admin add a new api key and save the record. Note in the database the value of settings.allowed_referers is null.
Open that same api user back up for editing. Add some values in the "Restrict Access to HTTP Referers" field. Save the record. Note that the value of settings.allowed_referers in the database is now an array of strings.
Open the same user again for editing. Remove all the values in the "Restrict Access to HTTP Referers" field. Save the record. Note that the value of settings.allowed_referers in the database is now [""] (an array containing an empty string).
So even though it looks like you've removed this setting from this specific key in the admin UI, there's actually this weird rogue empty string in the database. This value of an empty string messes with the referrer checks and essentially renders this specific key inoperable, since nothing matches this empty referrer value.
The text was updated successfully, but these errors were encountered:
GUI
added a commit
to NREL/api-umbrella-web
that referenced
this issue
Dec 7, 2014
settings.allowed_referers
is null.settings.allowed_referers
in the database is now an array of strings.settings.allowed_referers
in the database is now[""]
(an array containing an empty string).So even though it looks like you've removed this setting from this specific key in the admin UI, there's actually this weird rogue empty string in the database. This value of an empty string messes with the referrer checks and essentially renders this specific key inoperable, since nothing matches this empty referrer value.
The text was updated successfully, but these errors were encountered: