Keylcoak does not know if there is a legal user or an attacker. So showing a generic “invalid username or password” is the only option here.
mbonn
2
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| LDAP failed connection blocks login | 0 | 480 | October 5, 2022 | |
|
Unable to login to keycloak that's been integrated with AD with LOGIN_ERROR clientId=null messages
|
2 | 152 | January 3, 2025 | |
|
Urgen help needed for password verification via LDAP
|
0 | 741 | February 23, 2022 | |
| Active Directory federation | 3 | 296 | July 25, 2024 | |
| Solved: Cannot Login with LDAP User and Password | 1 | 684 | June 19, 2024 |