(oidc): Add support for loading tokens via a file, env var, and path in env var #5251
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…le, and from a file path set in an env var.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Thanks for this @Manouchehri |
|
Do let me know if any unit tests break on this in the future; I don't expect that to happen, but I'd be happy to fix it if it does. :) |
|
ci/cd looks smooth so far - thanks for the offer, though! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
Adds
oidc/env/{env_var_name},oidc/file/{temp_file_path}, andoidc/env_path/{env_var_name}support for OIDC flows.Relevant issues
Personally, I really recommend using stuff like
oidc/azure/instead, as that allows us to update it in the future if Azure ever changes their API..That said, PRs like #5131 show that people seem to really want to set their own custom OIDC variables, even if LiteLLM already supports their use-case.
There are some valid edge use-cases where I can see this being required. Everyone else reading this, should really use the
oidc/[provider]/[?audience]format unless you have a good reason not to.Type
🆕 New Feature
📖 Documentation
✅ Test
Changes
Adds support for using
oidc/env/{env_var_name},oidc/file/{temp_file_path}, andoidc/env_path/{env_var_name}, and