[JBoss JIRA] (WFCORE-1356) javax.sql.api should declare a dependency on javax.transaction.api
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1356?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-1356.
------------------------------
> javax.sql.api should declare a dependency on javax.transaction.api
> ------------------------------------------------------------------
>
> Key: WFCORE-1356
> URL: https://issues.jboss.org/browse/WFCORE-1356
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Priority: Blocker
>
> javax.sql.XAConnection (https://docs.oracle.com/javase/7/docs/api/javax/sql/XAConnection.html) depends on javax.transaction.xa.XAResource
> Including a partial stack trace that shows the failure:
> {quote}
> Caused by: java.lang.ClassNotFoundException: javax.transaction.xa.XAResource from [Module "javax.sql.api:main" from local module loader <SNIP/>
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-1083) Login Module is messed up when one of the module-option is empty
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1083?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-1083.
------------------------------
> Login Module is messed up when one of the module-option is empty
> ----------------------------------------------------------------
>
> Key: WFCORE-1083
> URL: https://issues.jboss.org/browse/WFCORE-1083
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: CentOS Linux release 7.1.1503 (Core)
> /usr/java/jdk1.8.0_45/
> WildFly 8.2.0
> Reporter: J Prasanna Venkatesan
> Assignee: Alexey Loubyansky
> Priority: Critical
>
> When one of the module-option is given as empty the whole login-module is messed up. But in real time there will be cases where the module-option can be empty. For Eg. while configuring org.jboss.security.auth.spi.LdapLoginModule, the principalDNPrefix can be empty
> *+Command with principalDNPrefix empty+*
> /subsystem=security/security-domain=SourceForge/authentication=classic/login-module=org.jboss.security.auth.spi.LdapLoginModule33:add(code=org.jboss.security.auth.spi.LdapLoginModule, flag=sufficient, module-options=[ "java.naming.provider.url" => "ldap://ldaphost.jboss.org:1", "java.naming.security.authentication" => "simple", *"principalDNPrefix" => ""*, "principalDNSuffix" => ",ou=People,o=jboss.org", "allowEmptyPasswords" => "false", "java.naming.factory.initial" => "com.sun.jndi.ldap.LdapCtxFactory", "throwValidateError" => "true" ]){allow-resource-service-restart=true}
> +Output in standalone-full.xml+
> Wrong value is stored as principalDNPrefix
> <login-module name="org.jboss.security.auth.spi.LdapLoginModule33" code="org.jboss.security.auth.spi.LdapLoginModule" flag="sufficient">
> <module-option name="java.naming.provider.url" value="ldap://ldaphost.jboss.org:1"/>
> <module-option name="java.naming.security.authentication" value="simple"/>
> *<module-option name="principalDNPrefix" value="principalDNSuffix"/>*
> <module-option name="allowEmptyPasswords" value="false"/>
> <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/>
> <module-option name="throwValidateError" value="true"/>
> </login-module>
> *+Command with principalDNPrefix with some value+*
> /subsystem=security/security-domain=SourceForge/authentication=classic/login-module=org.jboss.security.auth.spi.LdapLoginModule44:add(code=org.jboss.security.auth.spi.LdapLoginModule, flag=sufficient, module-options=[ "java.naming.provider.url" => "ldap://ldaphost.jboss.org:1", "java.naming.security.authentication" => "simple", *"principalDNPrefix" => "test"*, "principalDNSuffix" => ",ou=People,o=jboss.org", "allowEmptyPasswords" => "false", "java.naming.factory.initial" => "com.sun.jndi.ldap.LdapCtxFactory", "throwValidateError" => "true" ]){allow-resource-service-restart=true}
> +Output in standalone-full.xml+
> Values are stored correctly.
> <login-module name="org.jboss.security.auth.spi.LdapLoginModule44" code="org.jboss.security.auth.spi.LdapLoginModule" flag="sufficient">
> <module-option name="java.naming.provider.url" value="ldap://ldaphost.jboss.org:1"/>
> <module-option name="java.naming.security.authentication" value="simple"/>
> *<module-option name="principalDNPrefix" value="test"/>*
> <module-option name="principalDNSuffix" value=",ou=People,o=jboss.org"/>
> <module-option name="allowEmptyPasswords" value="false"/>
> <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/>
> <module-option name="throwValidateError" value="true"/>
> </login-module>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-9816) There are in doubt transactions after communication DB to EAP is halted
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9816?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9816:
-----------------------------
Fix Version/s: 12.0.0.Final
> There are in doubt transactions after communication DB to EAP is halted
> -----------------------------------------------------------------------
>
> Key: WFLY-9816
> URL: https://issues.jboss.org/browse/WFLY-9816
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 11.0.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Critical
> Fix For: 12.0.0.Final
>
>
> Implementation: JTS
> Priority is set to critical due to regression (issue is not seen in 7.0) and the fact that some inconsistency might be expected (communication from DB to EAP is halted - resource is commited, but TM doesn't know it)
> Failing tests:
> org.jboss.as.test.jbossts.crashrec.test.JMSProxyMdbMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA(org.jboss.as.test.jbossts.crashrec.test.JMSProxyMdbMessagingServerCrashRecoveryTestCase)
> Run 1: JMSProxyMdbMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA:276->TestBaseOneServer.checkIfTxLogsAreEmpty:564->TestBaseOneServer.checkIfTransactionManagerLogStoreIsEmpy:619 Recovery failed, some Uids still left in the tx log - number of pending uids before test: 0, pending uids after test: 1. Pending Uids are: 0:ffff7f000001:-5d473c0b:59afe2ee:69[["0:ffff7f000001:-5d473c0b:59afe2ee:7c"]],
> Run 2: JMSProxyMdbMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA JBoss log parsed file /home/istraka/repositories/jboss-other-repositories/tests-transactions/jbossts/target/jbossas-jbossts/standalone/log/JMSProxyMdbMessagingServerCrashRecoveryTestCase_haltConnectionAfterDbCommitsWithTestXA_jts_server.log contains not expected string XAException on line 11313 with text '2017-09-06 14:00:32,786 WARN [com.arjuna.ats.jtax] (Periodic Recovery) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_NOTA from resource XAResourceWrapperImpl@46c7baf5[xaResource=org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper(a)4d2dca8d pad=false overrideRmValue=null productName=ActiveMQ Artemis productVersion=2.0 jndiName=java:/JmsXA NodeId:846be472-92f7-11e7-b284-340286a805f7] in transaction < 131072, 32, 36, 0000000000-1-1127001-94-72-61-1189-81-30-1800010597889871, 0000000000-1-1127001-94-72-61-1189-81-30-1800012300000000 >: javax.transaction.xa.XAException'
> org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommits(org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase)
> Run 1: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommits:277->TestBaseOneServer.checkIfTxLogsAreEmpty:564->TestBaseOneServer.checkIfTransactionManagerLogStoreIsEmpy:619 Recovery failed, some Uids still left in the tx log - number of pending uids before test: 0, pending uids after test: 1. Pending Uids are: 0:ffff7f000001:-a865f1e:59afdfbb:64[["0:ffff7f000001:-a865f1e:59afdfbb:6e"]],
> Run 2: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommits JBoss log parsed file /home/istraka/repositories/jboss-other-repositories/tests-transactions/jbossts/target/jbossas-jbossts/standalone/log/JMSProxyMessagingServerCrashRecoveryTestCase_haltConnectionAfterDbCommits_jts_server.log contains not expected string XAException on line 5951 with text '2017-09-06 13:46:42,888 WARN [com.arjuna.ats.jtax] (Periodic Recovery) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_NOTA from resource XAResourceWrapperImpl@730871ea[xaResource=org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper(a)4028496b pad=false overrideRmValue=null productName=ActiveMQ Artemis productVersion=2.0 jndiName=java:/JmsXA NodeId:846be472-92f7-11e7-b284-340286a805f7] in transaction < 131072, 32, 36, 0000000000-1-1127001-11121-96-3089-81-33-6900010097889871, 0000000000-1-1127001-11121-96-3089-81-33-6900010900000000 >: javax.transaction.xa.XAException'
> org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA(org.jboss.as.test.jbossts.crashrec.test.JMSProxyMessagingServerCrashRecoveryTestCase)
> Run 1: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA:289->TestBaseOneServer.checkIfTxLogsAreEmpty:564->TestBaseOneServer.checkIfTransactionManagerLogStoreIsEmpy:619 Recovery failed, some Uids still left in the tx log - number of pending uids before test: 0, pending uids after test: 1. Pending Uids are: 0:ffff7f000001:4087749a:59afe058:64[["0:ffff7f000001:4087749a:59afe058:73"]],
> Run 2: JMSProxyMessagingServerCrashRecoveryTestCase.haltConnectionAfterDbCommitsWithTestXA JBoss log parsed file /home/istraka/repositories/jboss-other-repositories/tests-transactions/jbossts/target/jbossas-jbossts/standalone/log/JMSProxyMessagingServerCrashRecoveryTestCase_haltConnectionAfterDbCommitsWithTestXA_jts_server.log contains not expected string XAException on line 5996 with text '2017-09-06 13:49:18,766 WARN [com.arjuna.ats.jtax] (Periodic Recovery) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_NOTA from resource XAResourceWrapperImpl@1bb543cb[xaResource=org.jboss.activemq.artemis.wildfly.integration.WildFlyActiveMQXAResourceWrapper(a)1e73c422 pad=false overrideRmValue=null productName=ActiveMQ Artemis productVersion=2.0 jndiName=java:/JmsXA NodeId:846be472-92f7-11e7-b284-340286a805f7] in transaction < 131072, 32, 36, 0000000000-1-112700164-121116-10289-81-328800010097889871, 0000000000-1-112700164-121116-10289-81-328800011400000000 >: javax.transaction.xa.XAException'
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3728) DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3728?page=com.atlassian.jira.plugi... ]
Ilia Vassilev reassigned WFCORE-3728:
-------------------------------------
Assignee: (was: Darran Lofthouse)
> DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3728
> URL: https://issues.jboss.org/browse/WFCORE-3728
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.10.Final
> Reporter: Ilia Vassilev
>
> After running the enable-elytron.cli and removing the old
> picketbox security subsystem, the deployment fails as
> it cannot find java:jboss/DefaultJMSConnectionFactory.
> java:jboss/DefaultJMSConnectionFactory is defined in the messaging
> subsystem and the ee default-bindings.
> Removing it from the ee default-bindings lets the app deploy, but it looks like there is some
> issue as it should be bound and no errors/warnings being logged.
> {code}
> 2018-04-02 12:15:36,593 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "ejb-security.jar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" =>
> ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" =>
> ["jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory
> is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> 2018-04-02 12:15:36,603 INFO [org.jboss.as.server] (ServerService
> Thread Pool -- 42) WFLYSRV0010: Deployed "ejb-security.jar"
> (runtime-name : "ejb-security.jar")
> 2018-04-02 12:15:36,607 INFO [org.jboss.as.controller] (Controller Boot
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service
> jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing)
> dependents: [service
> jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3728) DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3728?page=com.atlassian.jira.plugi... ]
Ilia Vassilev moved ELY-1555 to WFCORE-3728:
--------------------------------------------
Project: WildFly Core (was: WildFly Elytron)
Key: WFCORE-3728 (was: ELY-1555)
Affects Version/s: 3.0.10.Final
(was: 1.1.9.Final)
> DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3728
> URL: https://issues.jboss.org/browse/WFCORE-3728
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.10.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> After running the enable-elytron.cli and removing the old
> picketbox security subsystem, the deployment fails as
> it cannot find java:jboss/DefaultJMSConnectionFactory.
> java:jboss/DefaultJMSConnectionFactory is defined in the messaging
> subsystem and the ee default-bindings.
> Removing it from the ee default-bindings lets the app deploy, but it looks like there is some
> issue as it should be bound and no errors/warnings being logged.
> {code}
> 2018-04-02 12:15:36,593 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "ejb-security.jar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" =>
> ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" =>
> ["jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory
> is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> 2018-04-02 12:15:36,603 INFO [org.jboss.as.server] (ServerService
> Thread Pool -- 42) WFLYSRV0010: Deployed "ejb-security.jar"
> (runtime-name : "ejb-security.jar")
> 2018-04-02 12:15:36,607 INFO [org.jboss.as.controller] (Controller Boot
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service
> jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing)
> dependents: [service
> jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ELY-1541) local-kerberos CredentialSource does not work with IBM java
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1541?page=com.atlassian.jira.plugin.s... ]
Jan Kalina updated ELY-1541:
----------------------------
Description:
When trying to connect as with Oracle JDK, following error occure:
{code}
Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: ELY05053: Callback handler failed for unknown reason: java.lang.reflect.UndeclaredThrowableException: org.ietf.jgss.GSSException, major code: 11, minor code: 0
major string: General failure, unspecified at GSSAPI level
minor string: Cannot get credential for principal default principal
{code}
-This is probably related to missing *useDefaultCcache* JAAS config (false by default):-
https://www.ibm.com/support/knowledgecenter/en/SSYKE2_6.0.0/com.ibm.java....
was:
Why trying to connect as with Oracle JDK, following error follows:
{code}
Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: ELY05053: Callback handler failed for unknown reason: java.lang.reflect.UndeclaredThrowableException: org.ietf.jgss.GSSException, major code: 11, minor code: 0
major string: General failure, unspecified at GSSAPI level
minor string: Cannot get credential for principal default principal
{code}
This is probably related to missing *useDefaultCcache* JAAS config (false by default):
https://www.ibm.com/support/knowledgecenter/en/SSYKE2_6.0.0/com.ibm.java....
> local-kerberos CredentialSource does not work with IBM java
> -----------------------------------------------------------
>
> Key: ELY-1541
> URL: https://issues.jboss.org/browse/ELY-1541
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credentials
> Affects Versions: 1.2.3.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Labels: ibm-java
>
> When trying to connect as with Oracle JDK, following error occure:
> {code}
> Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: ELY05053: Callback handler failed for unknown reason: java.lang.reflect.UndeclaredThrowableException: org.ietf.jgss.GSSException, major code: 11, minor code: 0
> major string: General failure, unspecified at GSSAPI level
> minor string: Cannot get credential for principal default principal
> {code}
> -This is probably related to missing *useDefaultCcache* JAAS config (false by default):-
> https://www.ibm.com/support/knowledgecenter/en/SSYKE2_6.0.0/com.ibm.java....
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (ELY-1541) local-kerberos CredentialSource does not work with IBM java
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1541?page=com.atlassian.jira.plugin.s... ]
Jan Kalina updated ELY-1541:
----------------------------
Comment: was deleted
(was: Also direct username+password for kerberos account can be passed into Kerberos - maybe we should allow this with AuthenticationContext callback handler:
{code:java}
LoginContext lc = new LoginContext("KDC", subject, (callbacks) -> {
// can be ommited if credential present in ccache
for (Callback c : callbacks) {
if (c instanceof NameCallback) {
((NameCallback)c).setName("hnelson(a)JBOSS.ORG");
} else if (c instanceof PasswordCallback) {
((PasswordCallback)c).setPassword("secret".toCharArray());
} else {
throw new UnsupportedCallbackException(c);
}
}
}, configuration);
{code})
> local-kerberos CredentialSource does not work with IBM java
> -----------------------------------------------------------
>
> Key: ELY-1541
> URL: https://issues.jboss.org/browse/ELY-1541
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credentials
> Affects Versions: 1.2.3.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Labels: ibm-java
>
> Why trying to connect as with Oracle JDK, following error follows:
> {code}
> Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: ELY05053: Callback handler failed for unknown reason: java.lang.reflect.UndeclaredThrowableException: org.ietf.jgss.GSSException, major code: 11, minor code: 0
> major string: General failure, unspecified at GSSAPI level
> minor string: Cannot get credential for principal default principal
> {code}
> This is probably related to missing *useDefaultCcache* JAAS config (false by default):
> https://www.ibm.com/support/knowledgecenter/en/SSYKE2_6.0.0/com.ibm.java....
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3568) Allow CLI output scrolling
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3568?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-3568:
-------------------------------
Issue Type: Feature Request (was: Enhancement)
> Allow CLI output scrolling
> --------------------------
>
> Key: WFCORE-3568
> URL: https://issues.jboss.org/browse/WFCORE-3568
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Affects Versions: 4.0.0.Alpha8
> Reporter: Chao Wang
> Assignee: Marek Marusic
>
> Mouse scrolling is forbidden to large CLI out. User has to press {{Down}} or {{Enter}} to navigate.
> It would be nice to allow fast scrolling or {{PgUp}} / {{PgDn}}. e.g.
> {noformat}
> [standalone@localhost:9990 /] /core-service=capability-registry:read-resource
> {
> "outcome" => "success",
> "result" => {
> "capabilities" => [
> {
> "name" => "org.wildfly.batch.configuration",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=batch-jberet"]
> },
> {
> "name" => "org.wildfly.batch.job.repository.in-memory",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=batch-jberet/in-memory-job-repository=in-memory"]
> },
> {
> "name" => "org.wildfly.batch.thread.pool.batch",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=batch-jberet/thread-pool=batch"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-group.ejb",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=ejb"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-group.server",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=server"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-group.web",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=web"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-node-factory.ejb",
> "dynamic" => false,
> "scope" => "global",
> "registration-points" => ["/subsystem=infinispan/cache-container=ejb"]
> },
> {
> "name" => "org.wildfly.clustering.cache.default-node-factory.server",
> "dynamic" => false,
> --More(2%)--
> {noformat}
> Also, after pressing {{Down}} or {{Enter}} to display more output, user can not press {{up}} to go up. User has to inconveniently use scroll up.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3727) NPE in io.undertow.security.impl.BasicAuthenticationMechanism.authenticate when picketbox subsystem removed
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3727?page=com.atlassian.jira.plugi... ]
Ilia Vassilev updated WFCORE-3727:
----------------------------------
Component/s: Security
> NPE in io.undertow.security.impl.BasicAuthenticationMechanism.authenticate when picketbox subsystem removed
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3727
> URL: https://issues.jboss.org/browse/WFCORE-3727
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ilia Vassilev
> Assignee: Stuart Douglas
>
> After enabling elytron, the security subsystem was removed. The war using jboss-web.xml security-domain looks like it is not used when the picketbox security subsystem is removed.
> {code}
> java.lang.NullPointerException
> at io.undertow.security.impl.BasicAuthenticationMechanism.authenticate(BasicAuthenticationMechanism.java:167)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:245)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:263)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:231)
> at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:125)
> at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:99)
> at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:92)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
> at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:330)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> The war has jboss-web.xml:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <security-domain>other</security-domain>
> </jboss-web>
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:undertow:4.0">
> ...
> <application-security-domains>
> <application-security-domain name="other" http-authentication-factory="application-http-authentication"/>
> </application-security-domains>
> </subsystem>
> <subsystem xmlns="urn:wildfly:elytron:1.2" final-providers="combined-providers" disallowed-providers="OracleUcrypto">
> ...
> <http>
> <http-authentication-factory name="application-http-authentication" http-server-mechanism-factory="global" security-domain="ApplicationDomain">
> <mechanism-configuration>
> <mechanism mechanism-name="BASIC">
> <mechanism-realm realm-name="Application Realm"/>
> </mechanism>
> <mechanism mechanism-name="FORM"/>
> </mechanism-configuration>
> </http-authentication-factory>
> <provider-http-server-mechanism-factory name="global"/>
> </http>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3727) NPE in io.undertow.security.impl.BasicAuthenticationMechanism.authenticate when picketbox subsystem removed
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3727?page=com.atlassian.jira.plugi... ]
Ilia Vassilev moved UNDERTOW-1327 to WFCORE-3727:
-------------------------------------------------
Project: WildFly Core (was: Undertow)
Key: WFCORE-3727 (was: UNDERTOW-1327)
> NPE in io.undertow.security.impl.BasicAuthenticationMechanism.authenticate when picketbox subsystem removed
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3727
> URL: https://issues.jboss.org/browse/WFCORE-3727
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Ilia Vassilev
> Assignee: Stuart Douglas
>
> After enabling elytron, the security subsystem was removed. The war using jboss-web.xml security-domain looks like it is not used when the picketbox security subsystem is removed.
> {code}
> java.lang.NullPointerException
> at io.undertow.security.impl.BasicAuthenticationMechanism.authenticate(BasicAuthenticationMechanism.java:167)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:245)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:263)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:231)
> at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:125)
> at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:99)
> at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:92)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
> at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:330)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> The war has jboss-web.xml:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <security-domain>other</security-domain>
> </jboss-web>
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:undertow:4.0">
> ...
> <application-security-domains>
> <application-security-domain name="other" http-authentication-factory="application-http-authentication"/>
> </application-security-domains>
> </subsystem>
> <subsystem xmlns="urn:wildfly:elytron:1.2" final-providers="combined-providers" disallowed-providers="OracleUcrypto">
> ...
> <http>
> <http-authentication-factory name="application-http-authentication" http-server-mechanism-factory="global" security-domain="ApplicationDomain">
> <mechanism-configuration>
> <mechanism mechanism-name="BASIC">
> <mechanism-realm realm-name="Application Realm"/>
> </mechanism>
> <mechanism mechanism-name="FORM"/>
> </mechanism-configuration>
> </http-authentication-factory>
> <provider-http-server-mechanism-factory name="global"/>
> </http>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months