-
-
Notifications
You must be signed in to change notification settings - Fork 723
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
Unable to disable api tokens in v5 #5087
Comments
Hey @dodgerbluee, if I'm reading your question correctly, this is about API keys and SDK clients. Unfortunately, there isn't really a way to do this with v4/v5 because Unleash expects to be able to work out what environment the SDK is requesting, which is part of the API token |
There isn't a way to only provide the first part of the api key? Since I am are migrating, its all under default |
Hi @dodgerbluee! 😊 Unfortunately, we need the entire API key for it to work correctly. |
Describe the bug
I'm trying to upgrade a v3 version of unleash to v5. I don't want to move all my application client sdks at once, and was hoping to disable the api token requirement until a later date. Maybe I'm reading into this wrong, but when I try to use authentication.enableApiToken or env. AUTH_ENABLE_API_TOKEN via https://docs.getunleash.io/reference/deploy/configuring-unleash, I still can't unleash without unauthorized messages.
Steps to reproduce the bug
No response
Expected behavior
No response
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
5.5.6
Subscription type
Open source
Hosting type
Self-hosted
SDK information (language and version)
No response
The text was updated successfully, but these errors were encountered: