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
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
I am not looking for support or already pursued the available support channels without success.
Version
2.38.0
Storage Type
In-memory
Installation Type
Official Helm chart
Expected Behavior
Retrieving Google Groups using configured GKE Workload Identity.
Actual Behavior
Dex is unable to start with error: failed to initialize server: server: Failed to open connector google: failed to open connector: failed to create connector google: could not create directory service: unable to parse client secret file to config: unexpected end of JSON input
Preflight Checklist
Version
2.38.0
Storage Type
In-memory
Installation Type
Official Helm chart
Expected Behavior
Retrieving Google Groups using configured GKE Workload Identity.
Actual Behavior
Dex is unable to start with error:
failed to initialize server: server: Failed to open connector google: failed to open connector: failed to create connector google: could not create directory service: unable to parse client secret file to config: unexpected end of JSON input
Steps To Reproduce
No response
Additional Information
This fails, because
google.FindDefaultCredentials(...)
(https://github.com/dexidp/dex/blob/master/connector/google/google.go#L363) executes successfully, but as docs say: JSON field may be nil when code is running on Google Cloud Platform (https://pkg.go.dev/golang.org/x/oauth2/google#Credentials). So empty JSON field is passed further togoogle.JWTConfigFromJSON(...)
(https://github.com/dexidp/dex/blob/master/connector/google/google.go#L374) and causes fail.Workload Identity is properly configured and verified by quering metadata server from dex pod.
Configuration
Logs
No response
The text was updated successfully, but these errors were encountered: