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 installed Headlamp and Dex using Helm in a Kubernetes environment. My goal is to integrate LDAP and enable LDAP login similar to ArgoCD. While Headlamp accesses Dex through the address headlamp.dashboard.svc.cluster.local, Dex cannot respond back to this address, so the process cannot be completed. How can I make Headlamp access Dex through a public URL (https://dashboard.company.com) ?
Note: This cannot be resolved with Dex redirectURIs.
Do you want to help fix this issue? Please see our contribution docs. For any non-trivial contributions, we advise you to join our our slack channel to discuss the implementation with Headlamp's core developers.
Additional Context
Result
If I add headlamp.dashboard.svc.cluster.local redirectURIs to dex config, here is result
The text was updated successfully, but these errors were encountered:
Describe the bug
I installed Headlamp and Dex using Helm in a Kubernetes environment. My goal is to integrate LDAP and enable LDAP login similar to ArgoCD. While Headlamp accesses Dex through the address
headlamp.dashboard.svc.cluster.local
, Dex cannot respond back to this address, so the process cannot be completed. How can I make Headlamp access Dex through a public URL (https://dashboard.company.com) ?Note: This cannot be resolved with Dex redirectURIs.
To Reproduce
Headlamp Helm Values
Dex Helm Values
If I enter my username password Dex not access
headlamp.dashboard.svc.cluster.local
Environment (please provide info about your environment):
Are you able to fix this issue?
Maybe
Additional Context
Result
If I add
headlamp.dashboard.svc.cluster.local
redirectURIs to dex config, here is resultThe text was updated successfully, but these errors were encountered: