-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Drone auth not working from ldap users. Internal users works #2743
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Any log on the console or file? |
Has user logged first in gitea or not? Give a try and tell us |
I've just tried, I can query that endpoint with an ldap user, no matter whether the user had first logged into gitea or not. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
I am using Gitea with LDAP and just set up drone.io Only problem is drone.io ignoring the second-factor authentication and logs in immediately, but i don't think this is a real issue as the auth is just using the LDAP behind right? |
logs in immediately? I don't get it to log in unless I remove the second factor |
Yes thats right. This is since drone release 1.0 i think. |
Closing this, as Drone 1.1.0 now supports using OAuth2 from Gitea, which supports connecting with any user incl. LDAP ones (also basic auth will soon be deprecated as a form of auth on Drone side). OAuth2 ensures that 2FA is followed. Please see https://discourse.drone.io/t/documentation-document-how-gogs-gitea-login-works/3762/7?u=techknowlogick for instructions on using oauth2 with Gitea/Drone. |
[x]
):Description
I have setup Drone CI with Gitea 1.2.1. Users use ldap athentication. When the user logs in to Drone, they receive a 401 Unauthorized response.
Users using the internal authentication are authorized in Drone without errors
Headers
Request auth, user hdhog use ldap auth
Response
Request auth, root user internal auth
Response:
The text was updated successfully, but these errors were encountered: