-
Bug
-
Resolution: Done
-
Major
-
None
-
None
The login method assumes the httpAuthenticator will have already been set:
@Override public boolean login(String username, String password) { if (httpAuthenticator == null) { log.trace("No HttpAuthenticator available for authentication."); return false; }
Instead we should adjust the code so the HttpAuthenticator will be created on demand for whichever method needs it first.
- incorporates
-
ELYWEB-133 SecurityContextImpl.login incorrectly assumes authenticate would be called first.
- Resolved
- is cloned by
-
JBEAP-21738 [GSS](7.4.z) ELYWEB-113 - SecurityContextImpl.login incorrectly assumes authenticate would be called first.
- Closed
- is incorporated by
-
JBEAP-21739 (7.3.z) Upgrade elytron-web from 1.6.2.Final-redhat-00001 to 1.6.3.Final-redhat-00001
- Closed
- is related to
-
JBEAP-22618 (7.3.z) WFLY-15009 - Test Case for ELYWEB-133 - SecurityContextImpl.login incorrectly assumes authenticate would be called first.
- Closed