Replies: 2 comments
-
|
Hello! About the second question, you can authenticate through a specific connector by providing a connector_id like For the first one, if I get it right, you can use the password credentials grant.
oauth2:
passwordConnector: ldap
curl -X POST 'http://127.0.0.1:5556/dex/token' \
--data 'grant_type=password' \
--data "client_id=example-app" \
--data "client_secret=ZXhhbXBsZS1hcHAtc2VjcmV0" \
--data "scope=openid" \
--data "username=admin@example.com" \
--data "password=password" |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @nabokihms, Let me reverse the order:
Thanks in advance! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I deployed Kubeflow with Dex authentication and added OpenLDAP connector to enable LDAP authentication. Now I would like to be able to access my Kubeflow programatically through LDAP. It seems that programmatic auth is a difficult topic for Dex and I only managed to find a workaround for basic auth, but maybe there's a way go also sign in using LDAP?
BTW The workaround from PR above looks good (username, password), but I have to be able to choose LDAP URL now as I have two different authentication methods. While main Dex dashboard is at
127.0.0.1for me, LDAP sign in page is athttp://127.0.0.1:8080/dex/auth/ldap?req=XXXXXXXXXXXXXXXwhere XXXX is a random token generated for each request. Just typinghttp://127.0.0.1:8080/dex/auth/ldapdoesn't work so I'm afraid I cannot hardcore the URL in my code.Beta Was this translation helpful? Give feedback.
All reactions