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
Currently OAuth2 tokens are supported if the input credentials cannot be parsed as JSON.
Unfortunately when using the source: Environment method of providing creds, the data goes through a different logic path and doesn't know to use OAuth2 if the data cannot be JSON parsed.
How can we reproduce it?
Use a provider config like above and put a valid oauth token into the env var.
What environment did it happen in?
Crossplane version:
Latest of Each -- Will flesh out shortly.
Cloud provider or hardware configuration
Kubernetes version (use kubectl version)
Kubernetes distribution (e.g. Tectonic, GKE, OpenShift)
OS (e.g. from /etc/os-release)
Kernel (e.g. uname -a)
The text was updated successfully, but these errors were encountered:
What happened?
I was trying to use an injected oauth2 token in an environment variable via a vault webhook and the following
ProviderConfig
Currently OAuth2 tokens are supported if the input credentials cannot be parsed as JSON.
Unfortunately when using the
source: Environment
method of providing creds, the data goes through a different logic path and doesn't know to use OAuth2 if the data cannot be JSON parsed.How can we reproduce it?
Use a provider config like above and put a valid oauth token into the env var.
What environment did it happen in?
Crossplane version:
Latest of Each -- Will flesh out shortly.
kubectl version
)uname -a
)The text was updated successfully, but these errors were encountered: