Legacy security behaviour changed compared to EAP 7.0. When there is no LDAP server reachable, attempt to acces management interface secured by legacy ldap security realm ends with http code 500. In EAP 7.0 it was 401. There is agreement between dev and qe, that 500 is more proper code as it express server side problem.
Therefore please document this change properly. Maybe worth adding into Migration guide.
- clones
-
JBEAP-8125 Document changed http status code in legacy ldap security realm if LDAP is unreachable
- Closed
- is related to
-
JBEAP-6402 Wrong HTTP error code for Elytron authentication when LDAP server is unreachable
- Closed