Can not see the reason of problems logging in using LDAP #3171

New Issue

GiteaMirror · 2025-11-02T05:02:40-06:00

GiteaMirror commented

2025-11-02 05:02:40 -06:00

Originally created by @iddm on GitHub (Apr 10, 2019).

When I have set up my LDAP authentication resource and suddenly in the LDAP records there was an account with the email already registered in the gitea itself without ldap, I could not log in using the LDAP credentials and it was really hard to find the reason for this problem. I had to dig the logs and to find out this problem, however, gitea could simply say something like "This account's email conflicts with another one. Check the logs". This would help a little bit, but now it just says "Invalid user name and/or password" which is absolutely incorrect because actually both username and password are correct indeed.

Gitea version (or commit ref): d7542bf
Git version: not relevant
Operating system: not relevant
Database (use [x]):
- PostgreSQL
- MySQL (MariaDB)
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Originally created by @iddm on GitHub (Apr 10, 2019). When I have set up my LDAP authentication resource and suddenly in the LDAP records there was an account with the email already registered in the gitea itself without ldap, I could not log in using the LDAP credentials and it was really hard to find the reason for this problem. I had to dig the logs and to find out this problem, however, gitea could simply say something like "This account's email conflicts with another one. Check the logs". This would help a little bit, but now it just says "Invalid user name and/or password" which is absolutely incorrect because actually both username and password **are** correct indeed. - Gitea version (or commit ref): d7542bf - Git version: not relevant - Operating system: not relevant - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL (MariaDB) - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant

GiteaMirror added the issue/stale label 2025-11-02 05:02:40 -06:00

GiteaMirror closed this issue

2025-11-02 05:02:40 -06:00

GiteaMirror commented

2025-11-02 05:02:40 -06:00

@lunny commented on GitHub (Apr 11, 2019):

Email is uniqued on database, we only know your account/password is not matched I think.

@lunny commented on GitHub (Apr 11, 2019): Email is uniqued on database, we only know your account/password is not matched I think.

GiteaMirror commented

2025-11-02 05:02:41 -06:00

@iddm commented on GitHub (Apr 11, 2019):

Email is uniqued on database, we only know your account/password is not matched I think.

I am not sure what does that mean. Do you mean you can't know what was the problem - mismatch of username and/or password or anything else? How do you log the error then? :)

@iddm commented on GitHub (Apr 11, 2019): > Email is uniqued on database, we only know your account/password is not matched I think. I am not sure what does that mean. Do you mean you can't know what was the problem - mismatch of username and/or password or anything else? How do you log the error then? :)

GiteaMirror commented

2025-11-02 05:02:41 -06:00

@stale[bot] commented on GitHub (Jun 10, 2019):

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.

@stale[bot] commented on GitHub (Jun 10, 2019): 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.

GiteaMirror commented

2025-11-02 05:02:41 -06:00

@stale[bot] commented on GitHub (Jun 24, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 24, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 05:02:41 -06:00

@iddm commented on GitHub (Jun 25, 2019):

So sad this has not even been considered.

@iddm commented on GitHub (Jun 25, 2019): So sad this has not even been considered.

GiteaMirror referenced this issue

2025-11-02 12:19:43 -06:00