[jboss-jira] [JBoss JIRA] (ELY-1202) match-purpose in Elytron authentication-context causes NPE
Ondrej Lukas created ELY-1202:
---------------------------------
Summary: match-purpose in Elytron authentication-context causes NPE
Key: ELY-1202
URL: https://issues.jboss.org/browse/ELY-1202
Project: WildFly Elytron
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Blocker
In case Elytron client authentication-context includes rule which contains
{{match-purpose}} then NullPointerException is thrown.
Thrown exception:
{code}
java.lang.NullPointerException
at java.lang.String.compareTo(String.java:1155)
at java.lang.String.compareTo(String.java:111)
at java.util.Arrays.binarySearch0(Arrays.java:2439)
at java.util.Arrays.binarySearch(Arrays.java:2379)
at org.wildfly.security.auth.client.MatchPurposeRule.matches(MatchPurposeRule.java:43)
at
org.wildfly.security.auth.client.AuthenticationContext.authRuleMatching(AuthenticationContext.java:233)
at
org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getAuthenticationConfiguration(AuthenticationContextConfigurationClient.java:125)
at
org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getAuthenticationConfiguration(AuthenticationContextConfigurationClient.java:107)
at
org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getAuthenticationConfiguration(AuthenticationContextConfigurationClient.java:92)
at
org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getAuthenticationConfiguration(AuthenticationContextConfigurationClient.java:79)
at
org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:151)
at
org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:117)
at
org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
at
org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
at
org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:162)
at
org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
at
org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:60)
at
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
at
org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
at
org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
... 42 more
{code}
We request blocker since it means that {{match-purpose}} rule matcher does not work at all
which breaks feature in RFE EAP7-567 and EAP7-568.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)