This can result in errors similar to:
java.lang.IllegalArgumentException: Parameter 'securityIdentity' may not be null at org.wildfly.common@1.7.0.Final-redhat-00003//org.wildfly.common.Assert.checkNotNullParamChecked(Assert.java:71) at org.wildfly.common@1.7.0.Final-redhat-00003//org.wildfly.common.Assert.checkNotNullParam(Assert.java:49) at org.wildfly.security.elytron-web.undertow-server@4.0.3.Final-redhat-00001//org.wildfly.elytron.web.undertow.server.ElytronAccount.<init>(ElytronAccount.java:50) at org.wildfly.security.elytron-web.undertow-server@4.0.3.Final-redhat-00001//org.wildfly.elytron.web.undertow.server.ElytronHttpExchange.authenticationComplete(ElytronHttpExchange.java:164) at org.wildfly.security.elytron-base@2.2.11.Final-redhat-00001//org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticationComplete(HttpAuthenticator.java:422) at org.wildfly.security.elytron-base@2.2.11.Final-redhat-00001//org.wildfly.security.http.HttpServerRequest.authenticationComplete(HttpServerRequest.java:129)
I would suggest within SecurityIdentityServerMechanismFactory.SecurityIdentityCallbackHandler at TRACE level (as this could be per request) log a warning if getSecurityIdentity has been called and a successful AuthenticationCompleteCallback has not already been intercepted.
NOTE: We presently have two variants of SecurityIdentityServerMechanismFactory, the log message should be added to both.
- blocks
-
JBEAP-30900 Add TRACE message warning if authenticationComplete called before
-
- Open
-
