ELY-271 mentions this error was happening because the org.wildfly.security.sasl.gssapi.GssapiClientFactory service was on the classpath, there was JBEAP-715 and JBEAP-5922 which got closed because of some packaging updates which removed the issue by removing it from the classpath or such.
The jboss-client.jar has:
- the class org.wildfly.security.sasl.gssapi.GssapiClientFactory
- the META-INF/services/javax.security.sasl.SaslClientFactory:org.wildfly.security.sasl.gssapi.GssapiClientFactory
So it looks like perhaps the services file should not list it? Should the class be included in the jboss-client.jar ?
Suppressed: javax.security.sasl.SaslException: ELY05108: [GSSAPI] Unable to create response token [Caused by javax.security.sasl.SaslException: ELY05127: [GSSAPI] No security layer supported by server but maximum message size received: "65536"] at org.wildfly.security.sasl.gssapi.GssapiClient.evaluateMessage(GssapiClient.java:307) at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180) at org.wildfly.security.sasl.gssapi.GssapiClient.evaluateChallenge(GssapiClient.java:212) at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54) at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55) at java.security.AccessController.doPrivileged(Native Method) at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.lambda$handleEvent$0(ClientConnectionOpenListener.java:650) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949) ... 3 more Caused by: javax.security.sasl.SaslException: ELY05127: [GSSAPI] No security layer supported by server but maximum message size received: "65536" at org.wildfly.security.sasl.gssapi.GssapiClient.evaluateMessage(GssapiClient.java:275) ... 11 more Suppressed: javax.security.sasl.SaslException: PLAIN: Server rejected authentication at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:736) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:578) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
- is related to
-
ELY-271 EJB authentication via Kerberos does not work with wildfly-security-api
- Resolved
-
JBEAP-5922 EJB authentication with Kerberos does not work in EAP 7.1.0.DR4
- Closed
-
JBEAP-715 EJB authentication via Kerberos does not work with wildfly-security-api
- Closed