[JBoss JIRA] (ISPN-4224) Kerberos auth IT fails on JDK8
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-4224?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-4224:
------------------------------
Status: Resolved (was: Pull Request Sent)
Assignee: Vojtech Juranek (was: Gustavo Fernandes)
Fix Version/s: 7.0.0.Alpha5
Resolution: Done
> Kerberos auth IT fails on JDK8
> ------------------------------
>
> Key: ISPN-4224
> URL: https://issues.jboss.org/browse/ISPN-4224
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
> Fix For: 7.0.0.Alpha5
>
>
> [Kerberos auth integration test|https://github.com/infinispan/infinispan/blob/master/integrationtest...] passes on JDK7, but fails on JDK8 with
> {noformat}
> Caused by: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.b5efb5d4-0f0d-448f-b60f-e8bd15023ebd.war:main" from Service Module Loader [Root exception is javax.naming.CommunicationException: Request: 1 cancelled]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:116)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:99)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:90)
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
> at javax.naming.InitialContext.init(InitialContext.java:242)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.security.negotiation.AdvancedLdapLoginModule.constructLdapContext(AdvancedLdapLoginModule.java:431)
> ... 109 more
> Caused by: javax.naming.CommunicationException: Request: 1 cancelled
> at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:105)
> at com.sun.jndi.ldap.Connection.readReply(Connection.java:449)
> at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:364)
> at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:126)
> at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:235)
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2740)
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114)
> ... 118 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ISPN-4224) Kerberos auth IT fails on JDK8
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4224?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-4224:
---------------------------------------
Assignee: Gustavo Fernandes (was: Vojtech Juranek)
> Kerberos auth IT fails on JDK8
> ------------------------------
>
> Key: ISPN-4224
> URL: https://issues.jboss.org/browse/ISPN-4224
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Vojtech Juranek
> Assignee: Gustavo Fernandes
>
> [Kerberos auth integration test|https://github.com/infinispan/infinispan/blob/master/integrationtest...] passes on JDK7, but fails on JDK8 with
> {noformat}
> Caused by: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.b5efb5d4-0f0d-448f-b60f-e8bd15023ebd.war:main" from Service Module Loader [Root exception is javax.naming.CommunicationException: Request: 1 cancelled]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:116)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:99)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:90)
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
> at javax.naming.InitialContext.init(InitialContext.java:242)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.security.negotiation.AdvancedLdapLoginModule.constructLdapContext(AdvancedLdapLoginModule.java:431)
> ... 109 more
> Caused by: javax.naming.CommunicationException: Request: 1 cancelled
> at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:105)
> at com.sun.jndi.ldap.Connection.readReply(Connection.java:449)
> at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:364)
> at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:126)
> at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:235)
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2740)
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114)
> ... 118 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ISPN-4299) Authentication configuration builder requires CallbackHandle also when subject it set
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-4299?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-4299:
------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Beta1
Resolution: Done
> Authentication configuration builder requires CallbackHandle also when subject it set
> -------------------------------------------------------------------------------------
>
> Key: ISPN-4299
> URL: https://issues.jboss.org/browse/ISPN-4299
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Vojtech Juranek
> Assignee: Tristan Tarrant
> Priority: Minor
> Fix For: 7.0.0.Beta1
>
>
> Authentication configuration builder allows to setup direcly subject under which action are performed. In this case there's no need for any additional authentication. However authentication configuration builder requires {{CallbackHandler}} also in this case and without it it fails with
> {noformat}
> org.infinispan.commons.CacheConfigurationException: ISPN004030: Cannot enable authentication without specifying a Callback Handler
> at org.infinispan.client.hotrod.configuration.AuthenticationConfigurationBuilder.validate(AuthenticationConfigurationBuilder.java:86)
> at org.infinispan.client.hotrod.configuration.SecurityConfigurationBuilder.validate(SecurityConfigurationBuilder.java:43)
> at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.validate(ConfigurationBuilder.java:280)
> at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.build(ConfigurationBuilder.java:314)
> at org.infinispan.client.hotrod.configuration.ConfigurationBuilder.build(ConfigurationBuilder.java:309)
> at org.infinispan.server.test.client.hotrod.security.HotRodSaslAuthTestBase.getRemoteCacheManagerConfig(HotRodSaslAuthTestBase.java:104)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ISPN-4224) Kerberos auth IT fails on JDK8
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4224?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-4224:
-----------------------------------------
I have failures both in jdk1.7 and 1.8.
The test fails during authentication because the Kerberos server has no knowledge of the "Realm" or "KDC" (at least in my environment)
>From the embedded Apache Directory Server logs:
{code}
Caused by: javax.security.sasl.SaslException: Failure to initialize security context [Caused by GSSException: Invalid name provided (Mechanism level: Cannot locate default realm)]
at com.sun.security.sasl.gsskerb.GssKrb5Server.<init>(GssKrb5Server.java:113)
at com.sun.security.sasl.gsskerb.FactoryImpl.createSaslServer(FactoryImpl.java:85)
at javax.security.sasl.Sasl.createSaslServer(Sasl.java:509)
at org.apache.directory.server.ldap.handlers.sasl.gssapi.GssapiMechanismHandler$1.run(GssapiMechanismHandler.java:78)
at org.apache.directory.server.ldap.handlers.sasl.gssapi.GssapiMechanismHandler$1.run(GssapiMechanismHandler.java:75)
... 19 more
Caused by: GSSException: Invalid name provided (Mechanism level: Cannot locate default realm)
at sun.security.jgss.krb5.Krb5NameElement.getInstance(Krb5NameElement.java:127)
at sun.security.jgss.krb5.Krb5MechFactory.getNameElement(Krb5MechFactory.java:95)
at sun.security.jgss.GSSManagerImpl.getNameElement(GSSManagerImpl.java:202)
at sun.security.jgss.GSSNameImpl.getElement(GSSNameImpl.java:472)
at sun.security.jgss.GSSNameImpl.init(GSSNameImpl.java:201)
at sun.security.jgss.GSSNameImpl.<init>(GSSNameImpl.java:170)
at sun.security.jgss.GSSManagerImpl.createName(GSSManagerImpl.java:137)
at com.sun.security.sasl.gsskerb.GssKrb5Server.<init>(GssKrb5Server.java:93)
... 23 more
{code}
I've created a pull request that solve the issue for me, please take a look if it works for you in both 1.7 and 1.8
> Kerberos auth IT fails on JDK8
> ------------------------------
>
> Key: ISPN-4224
> URL: https://issues.jboss.org/browse/ISPN-4224
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
>
> [Kerberos auth integration test|https://github.com/infinispan/infinispan/blob/master/integrationtest...] passes on JDK7, but fails on JDK8 with
> {noformat}
> Caused by: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.b5efb5d4-0f0d-448f-b60f-e8bd15023ebd.war:main" from Service Module Loader [Root exception is javax.naming.CommunicationException: Request: 1 cancelled]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:116)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:99)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:90)
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
> at javax.naming.InitialContext.init(InitialContext.java:242)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.security.negotiation.AdvancedLdapLoginModule.constructLdapContext(AdvancedLdapLoginModule.java:431)
> ... 109 more
> Caused by: javax.naming.CommunicationException: Request: 1 cancelled
> at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:105)
> at com.sun.jndi.ldap.Connection.readReply(Connection.java:449)
> at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:364)
> at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:126)
> at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:235)
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2740)
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114)
> ... 118 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ISPN-4224) Kerberos auth IT fails on JDK8
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4224?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-4224:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2586
> Kerberos auth IT fails on JDK8
> ------------------------------
>
> Key: ISPN-4224
> URL: https://issues.jboss.org/browse/ISPN-4224
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
>
> [Kerberos auth integration test|https://github.com/infinispan/infinispan/blob/master/integrationtest...] passes on JDK7, but fails on JDK8 with
> {noformat}
> Caused by: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.b5efb5d4-0f0d-448f-b60f-e8bd15023ebd.war:main" from Service Module Loader [Root exception is javax.naming.CommunicationException: Request: 1 cancelled]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:116)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:99)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:90)
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
> at javax.naming.InitialContext.init(InitialContext.java:242)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
> at org.jboss.security.negotiation.AdvancedLdapLoginModule.constructLdapContext(AdvancedLdapLoginModule.java:431)
> ... 109 more
> Caused by: javax.naming.CommunicationException: Request: 1 cancelled
> at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:105)
> at com.sun.jndi.ldap.Connection.readReply(Connection.java:449)
> at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:364)
> at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:126)
> at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:235)
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2740)
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114)
> ... 118 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ISPN-4329) Protostream invokes TagHandler.onStart() more than once
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-4329?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-4329:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Integrated in protostream 1.0.x and master
> Protostream invokes TagHandler.onStart() more than once
> -------------------------------------------------------
>
> Key: ISPN-4329
> URL: https://issues.jboss.org/browse/ISPN-4329
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 7.0.0.Alpha4
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 7.0.0.Beta1
>
>
> onStart() should be called exactly once, at the beginning of the parse process of the top-level message but it is actually called also every time a nested message is parsed. This was harmless until now because none of our handlers performed anything in onStart().
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month
[JBoss JIRA] (ISPN-4329) Protostream invokes TagHandler.onStart() more than once
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-4329:
-----------------------------------
Summary: Protostream invokes TagHandler.onStart() more than once
Key: ISPN-4329
URL: https://issues.jboss.org/browse/ISPN-4329
Project: Infinispan
Issue Type: Bug
Components: Remote Querying
Affects Versions: 7.0.0.Alpha4
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 7.0.0.Beta1
onStart() should be called exactly once, at the beginning of the parse process of the top-level message but it is actually called also every time a nested message is parsed. This was harmless until now because none of our handlers performed anything in onStart().
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 1 month