[JBoss JIRA] (WFLY-10533) JASPI mech shows error message in FORM authentication
by Hisanobu Okuda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10533?page=com.atlassian.jira.plugin... ]
Hisanobu Okuda updated WFLY-10533:
----------------------------------
Attachment: test.war
> JASPI mech shows error message in FORM authentication
> -----------------------------------------------------
>
> Key: WFLY-10533
> URL: https://issues.jboss.org/browse/WFLY-10533
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 14.0.0.CR1
> Environment: - WF 14.0.0.Beta1
> - EAP 7.1.x
> Reporter: Hisanobu Okuda
> Assignee: Darran Lofthouse
> Attachments: test.war
>
>
> When JASPI is used for web application with FORM authentication, an exception is thrown and the following error message is shown:
> {code}
> 17:26:36,248 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /test/login.html: java.lang.IllegalStateException: UT000002: The response has already been started
> at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1406)
> at io.undertow.server.HttpServerExchange.setResponseCode(HttpServerExchange.java:1381)
> at org.wildfly.extension.undertow.security.jaspi.JASPICAuthenticationMechanism.authenticate(JASPICAuthenticationMechanism.java:155)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:245)
> 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.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> 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.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jaspi.JASPICSecureResponseHandler.handleRequest(JASPICSecureResponseHandler.java:48)
> 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.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
> 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:360)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10545) JASPI mech shows error message in FORM authentication
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created WFLY-10545:
-------------------------------------
Summary: JASPI mech shows error message in FORM authentication
Key: WFLY-10545
URL: https://issues.jboss.org/browse/WFLY-10545
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 14.0.0.CR1
Environment: - WF 14.0.0.Beta1
- EAP 7.1.x
Reporter: Hisanobu Okuda
Assignee: Darran Lofthouse
When JASPI is used for web application with FORM authentication, an exception is thrown and the following error message is shown:
{code}
17:26:36,248 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /test/login.html: java.lang.IllegalStateException: UT000002: The response has already been started
at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1406)
at io.undertow.server.HttpServerExchange.setResponseCode(HttpServerExchange.java:1381)
at org.wildfly.extension.undertow.security.jaspi.JASPICAuthenticationMechanism.authenticate(JASPICAuthenticationMechanism.java:155)
at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:245)
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.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
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.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at org.wildfly.extension.undertow.security.jaspi.JASPICSecureResponseHandler.handleRequest(JASPICSecureResponseHandler.java:48)
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.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1514)
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:360)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2532:
-------------------------------------
[~danielezonca] [~jomarko] [~porcelli] I updated the click-thru with the following changes:
Interaction mechanism:
* Inline cell editing.
* Right dock properties panel with expression editor, as alternative input option for users who need more guidance.
* Single object selection only. To add multiple Given/Expect statements, user will need to edit the table to add columns then select the object.
Results view at the Asset level
* Alerts panel - scenario alerts take formatting of alerts table but are placed in a separatetest tab.
* Right panel Test results summary.
* Table cell highlighting for objects with errors.
Results view at the Project level.
* No right panel.
* All test results in alert panel, in error/alert format but in separate tab.
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: Appformer, UX, UXTeam
> Attachments: Proposed.pdf
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide wireframe design and click-thru prototype which includes the following views:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2532:
--------------------------------
Attachment: Proposed.pdf
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: Appformer, UX, UXTeam
> Attachments: Proposed.pdf
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide wireframe design and click-thru prototype which includes the following views:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2532:
--------------------------------
Attachment: (was: DRAFT1.pdf)
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: Appformer, UX, UXTeam
> Attachments: Proposed.pdf
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide wireframe design and click-thru prototype which includes the following views:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SECURITY-991) NPE When registering null AuthConfigProvider on JBossAuthConfigFactory
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/SECURITY-991?page=com.atlassian.jira.plug... ]
Ilia Vassilev updated SECURITY-991:
-----------------------------------
Description:
The following NPE is reported where the AuthConfigProvider is null: -
{noformat}
2018-06-11 02:56:31,054 ERROR [stderr] (default task-1) java.lang.NullPointerException
2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at org.jboss.security.auth.message.config.JBossAuthConfigFactory.registerConfigProvider(JBossAuthConfigFactory.java:250)
{noformat}
However within JASPIC the null AuthConfigProvider has special meaning.
was:
The following NPE is reported where the AuthConfigFactory is null: -
{noformat}
2018-06-11 02:56:31,054 ERROR [stderr] (default task-1) java.lang.NullPointerException
2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at org.jboss.security.auth.message.config.JBossAuthConfigFactory.registerConfigProvider(JBossAuthConfigFactory.java:250)
{noformat}
However within JASPIC the null AuthConfigFactory has special meaning.
> NPE When registering null AuthConfigProvider on JBossAuthConfigFactory
> ----------------------------------------------------------------------
>
> Key: SECURITY-991
> URL: https://issues.jboss.org/browse/SECURITY-991
> Project: PicketBox
> Issue Type: Bug
> Components: JBossSX
> Affects Versions: PicketBox_5_1_0.Final
> Reporter: Darran Lofthouse
> Assignee: Ilia Vassilev
> Fix For: PicketBox_5_1_1.Beta1
>
>
> The following NPE is reported where the AuthConfigProvider is null: -
> {noformat}
> 2018-06-11 02:56:31,054 ERROR [stderr] (default task-1) java.lang.NullPointerException
> 2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
> 2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
> 2018-06-11 02:56:31,055 ERROR [stderr] (default task-1) at org.jboss.security.auth.message.config.JBossAuthConfigFactory.registerConfigProvider(JBossAuthConfigFactory.java:250)
> {noformat}
> However within JASPIC the null AuthConfigProvider has special meaning.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFWIP-20) [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
by Justin Bertram (JIRA)
[ https://issues.jboss.org/browse/WFWIP-20?page=com.atlassian.jira.plugin.s... ]
Justin Bertram edited comment on WFWIP-20 at 6/11/18 5:09 PM:
--------------------------------------------------------------
I was able to reproduce the failure using the steps provided. However, I wanted to focus on the system property test so I ran that one by itself:
{noformat}
mvn clean test -Dtest=ClientThreadPoolTestCase#testGlobalPoolsConfiguredBySystemProperty -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT -DfailIfNoTests=true | tee log
{noformat}
As Jeff noted, the test runs, but it doesn't fail. I ran it several times and it always passed. I suspect there may be an issue with the test itself.
[~jmesnil], I also looked into {{org.apache.activemq.artemis.ClientThreadPoolsTest#testSystemPropertyThreadPoolSettings}} in the Artemis code-base and it passes as expected, ensuring the thread pool doesn't grow beyond the value specified by the system property.
was (Author: jbertram):
I was able to reproduce the failure using the steps provided. However, I wanted to focus on the system property test so I ran that one by itself:
{noformat}
mvn clean test -Dtest=ClientThreadPoolTestCase#testGlobalPoolsConfiguredBySystemProperty -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT -DfailIfNoTests=true | tee log
{noformat}
As Jeff noted, the test runs, but it doesn't fail. I ran it several times and it always passed. I suspect there may be an issue with the test itself.
[~jmesnil], I also looked into {{org.apache.activemq.artemis.ClientThreadPoolsTest#testSystemPropertyThreadPoolSettings}} in the Artemis code-base and it passes as expected.
> [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored
> ------------------------------------------------------------------------------------------------
>
> Key: WFWIP-20
> URL: https://issues.jboss.org/browse/WFWIP-20
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> Setting client globalThreadPoolSize for configuring max number of ActiveMQ-client-global-threads using system property or in connection factory which is looked up by standalone JMS client is ignored. There is alway 8 * number CPU cores.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month