April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-508) A USERNAME HTTP authentication mechanism.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-508: ------------------------------------ Summary: A USERNAME HTTP authentication mechanism. Key: ELY-508 URL: https://issues.jboss.org/browse/ELY-508 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP Reporter: Darran Lofthouse Fix For: 2.0.0.Alpha1 This is closely related to FORM authentication but to cover the case where we want to prompt for just a username first and once we know that the subsequent challenge can be customised. The customisation may be by separate authentication mechanisms then able to offer their own specific FORM variant and perform their own validation. As an example we may prompt one user for a password whilst prompt a different user for a password and a OTP, we could even use this to decide if we authenticate against a local realm with a credential or redirect via something like KeyCloak. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (AS7-1663) An extended persistence context should not be propagated if there is no JTA transaction

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-1663?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-1663: ----------------------------------- updated link to AS7-1663 commit is https://github.com/wildfly/wildfly/commit/db8aec0d89c08a09e85ec4239402ba7... > An extended persistence context should not be propagated if there is no JTA transaction > --------------------------------------------------------------------------------------- > > Key: AS7-1663 > URL: https://issues.jboss.org/browse/AS7-1663 > Project: Application Server 7 > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 7.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 7.0.2.Final > > > JPA 2.0 specification section 7.6.3.1 Requirements for Persistence Context Propagation: > " > Persistence contexts are propagated by the container across component invocations as follows. > If a component is called and there is no JTA transaction or the JTA transaction is not propagated, the > persistence context is not propagated. > " > For the case of a SFSB (with an extended persistence context XPC) method that is not in a JTA transaction, invoking a SLSB (with a transactional entity manager PC) method that requires a transaction. The SLSB method should not use the extended persistence context but should instead start a new persistence context instead for the duration of the SLSB transaction (will end at the method end). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (AS7-1663) An extended persistence context should not be propagated if there is no JTA transaction

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-1663?page=com.atlassian.jira.plugin.s... ] Scott Marlow closed AS7-1663. ----------------------------- > An extended persistence context should not be propagated if there is no JTA transaction > --------------------------------------------------------------------------------------- > > Key: AS7-1663 > URL: https://issues.jboss.org/browse/AS7-1663 > Project: Application Server 7 > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 7.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 7.0.2.Final > > > JPA 2.0 specification section 7.6.3.1 Requirements for Persistence Context Propagation: > " > Persistence contexts are propagated by the container across component invocations as follows. > If a component is called and there is no JTA transaction or the JTA transaction is not propagated, the > persistence context is not propagated. > " > For the case of a SFSB (with an extended persistence context XPC) method that is not in a JTA transaction, invoking a SLSB (with a transactional entity manager PC) method that requires a transaction. The SLSB method should not use the extended persistence context but should instead start a new persistence context instead for the duration of the SLSB transaction (will end at the method end). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6544) Mistake in the English text, shown in the browser (while still booting)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6544?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6544: ------------------------------ Labels: task (was: new_and_noteworthy task) > Mistake in the English text, shown in the browser (while still booting) > ----------------------------------------------------------------------- > > Key: WFLY-6544 > URL: https://issues.jboss.org/browse/WFLY-6544 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Zahra Ahmadi > Assignee: Jason Greene > Priority: Minor > Labels: task > Attachments: typo-Bug.png > > > While Wildfly is restarting, and not up yet, the following message is shown in the browser: > --------- > *The management interface could not be loaded.* > Service temporarily unavailable. Is the server is still booting? > --------- > There is an extra *is* before 'still'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6544) Mistake in the English text, shown in the browser (while still booting)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6544?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6544: ------------------------------ Issue Type: Task (was: Feature Request) > Mistake in the English text, shown in the browser (while still booting) > ----------------------------------------------------------------------- > > Key: WFLY-6544 > URL: https://issues.jboss.org/browse/WFLY-6544 > Project: WildFly > Issue Type: Task > Components: Web Console > Reporter: Zahra Ahmadi > Assignee: Jason Greene > Priority: Minor > Labels: task > Attachments: typo-Bug.png > > > While Wildfly is restarting, and not up yet, the following message is shown in the browser: > --------- > *The management interface could not be loaded.* > Service temporarily unavailable. Is the server is still booting? > --------- > There is an extra *is* before 'still'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6544) Mistake in the English text, shown in the browser (while still booting)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6544?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-6544: --------------------------------- Assignee: Harald Pehl (was: Jason Greene) > Mistake in the English text, shown in the browser (while still booting) > ----------------------------------------------------------------------- > > Key: WFLY-6544 > URL: https://issues.jboss.org/browse/WFLY-6544 > Project: WildFly > Issue Type: Task > Components: Web Console > Reporter: Zahra Ahmadi > Assignee: Harald Pehl > Priority: Minor > Labels: task > Attachments: typo-Bug.png > > > While Wildfly is restarting, and not up yet, the following message is shown in the browser: > --------- > *The management interface could not be loaded.* > Service temporarily unavailable. Is the server is still booting? > --------- > There is an extra *is* before 'still'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6544) Mistake in the English text, shown in the browser (while still booting)

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6544?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6544: ------------------------------ Component/s: Web Console > Mistake in the English text, shown in the browser (while still booting) > ----------------------------------------------------------------------- > > Key: WFLY-6544 > URL: https://issues.jboss.org/browse/WFLY-6544 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Zahra Ahmadi > Assignee: Jason Greene > Priority: Minor > Labels: task > Attachments: typo-Bug.png > > > While Wildfly is restarting, and not up yet, the following message is shown in the browser: > --------- > *The management interface could not be loaded.* > Service temporarily unavailable. Is the server is still booting? > --------- > There is an extra *is* before 'still'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1136) Get rid of the droolsjbpm-build-distribution git repository

by Petr Široký (JIRA)

Petr Široký created DROOLS-1136: ----------------------------------- Summary: Get rid of the droolsjbpm-build-distribution git repository Key: DROOLS-1136 URL: https://issues.jboss.org/browse/DROOLS-1136 Project: Drools Issue Type: Task Reporter: Petr Široký Assignee: Petr Široký The repository https://github.com/droolsjbpm/droolsjbpm-build-distribution contains only single module. We need to migrate the stuff from there into different repository as we currently have way too many git repos to care about and this one seems like obvious candidate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-5930) Unable to load deployments

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5930?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-5930: ----------------------------------- What is interesting is the line where this happens. https://github.com/wildfly/wildfly/blob/master/undertow/src/main/java/org... and this could only happen if deployment service is not available aka deployment is not properly deployed. We could add some more safe guards to this code, but without a reproducer it would be futile. > Unable to load deployments > -------------------------- > > Key: WFLY-5930 > URL: https://issues.jboss.org/browse/WFLY-5930 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Web (Undertow) > Affects Versions: 9.0.2.Final > Reporter: Hamed Abdollahpour > Assignee: Tomaz Cerar > > Fail to get list of deployment on application server with this error: > 12:19:40,130 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-3) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("deployment" => "discripto-ear.ear"), > ("subdeployment" => "discripto-rest.war"), > ("subsystem" => "undertow"), > ("servlet" => "com.wpic.discripto.rest.App") > ]): java.lang.NullPointerException > at org.wildfly.extension.undertow.DeploymentServletDefinition$AbstractMetricsHandler.execute(DeploymentServletDefinition.java:121) > at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:174) > at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:137) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:196) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AvailableResponseWrapper.execute(GlobalOperationHandlers.java:641) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:803) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1183) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:218) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:208) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:95) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > 12:21:20,258 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-2) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("deployment" => "discripto-ear.ear"), > ("subdeployment" => "discripto-rest.war"), > ("subsystem" => "undertow"), > ("servlet" => "com.wpic.discripto.rest.App") > ]): java.lang.NullPointerException > at org.wildfly.extension.undertow.DeploymentServletDefinition$AbstractMetricsHandler.execute(DeploymentServletDefinition.java:121) > at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:174) > at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:137) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:196) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AvailableResponseWrapper.execute(GlobalOperationHandlers.java:641) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:803) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1183) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:218) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:208) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:95) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > It works perfect after restarting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-334) Tests are relying on the platform default charset

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-334?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reassigned ELY-334: ------------------------------ Assignee: Jan Kalina > Tests are relying on the platform default charset > ------------------------------------------------- > > Key: ELY-334 > URL: https://issues.jboss.org/browse/ELY-334 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Reporter: David Lloyd > Assignee: Jan Kalina > Priority: Minor > > There are a number of uses of {{String(byte[])}} which assume the platform default charset is ASCII-derived. These need to be changed to specify {{StandardCharsets.UTF_8}} as the second method argument. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2016