Ivar Conradi Østhus 4a81f0932f fix: Allow AuthType None to use valid API tokens (#6247) ... Fixes ##5799 and #5785 When you do not provide a token we should resolve to the "default" environment to maintain backward compatibility. If you actually provide a token we should prefer that and even block the request if it is not valid. An interesting fact is that "default" environment is not available on a fresh installation of Unleash. This means that you need to provide a token to actually get access to toggle configurations. --------- Co-authored-by: Thomas Heartman <thomas@getunleash.io>		2024-02-16 08:24:56 +00:00
..
contributing	docs: Delete old preferred-styles-import-placement (#6185)	2024-02-09 17:50:08 +01:00
feature-flag-tutorials	docs: Python Examples page (#6094)	2024-02-01 17:08:49 -05:00
how-to	docs: spelling and grammar (#6007)	2024-01-23 19:52:10 +01:00
migrations
reference	fix: misc UI/UX fixes (#6241)	2024-02-15 08:17:11 +00:00
topics	docs: update images in feature flags best practices to work on dark backgrounds (#6168)	2024-02-09 09:39:40 +09:00
understanding-unleash	docs: Minor typos (#6014)	2024-01-23 20:19:06 +01:00
unleash-academy	docs: change "time burden" to "time investment" (#6079)	2024-01-31 10:48:28 +00:00
using-unleash	fix: Allow AuthType None to use valid API tokens (#6247)	2024-02-16 08:24:56 +00:00
client-specification.md
quickstart.md	docs: add missing full stop	2024-02-14 11:45:00 +09:00
welcome.md