June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13492) Upgrade Wildfly HTTP Client to 1.1.1.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13492?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13492: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Upgrade Wildfly HTTP Client to 1.1.1.Final > ------------------------------------------ > > Key: WFLY-13492 > URL: https://issues.redhat.com/browse/WFLY-13492 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Fix For: 21.0.0.Beta1 > > > Upgrade WildFly HTTP Client to 1.0.18.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12654) Switch from javax.jws:jsr181-api to jakarta.jws:jakarta.jws-api

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12654?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12654: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Switch from javax.jws:jsr181-api to jakarta.jws:jakarta.jws-api > --------------------------------------------------------------- > > Key: WFLY-12654 > URL: https://issues.redhat.com/browse/WFLY-12654 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Scott Marlow > Assignee: Parul Sharma > Priority: Major > Fix For: 21.0.0.Beta1 > > > Update WildFly to use jakarta.jws:jakarta.jws-api from https://github.com/eclipse-ee4j/jws-api, note that version 2.1 is not yet available as mentioned on [https://github.com/eclipse-ee4j/jws-api/issues/48]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13435) Update Undertow / Elytron Integration to use SecurityMetaData in DeploymentUnit

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13435?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13435: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Update Undertow / Elytron Integration to use SecurityMetaData in DeploymentUnit > ------------------------------------------------------------------------------- > > Key: WFLY-13435 > URL: https://issues.redhat.com/browse/WFLY-13435 > Project: WildFly > Issue Type: Task > Components: Security, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Beta1 > > > WFCORE-4962 is adding a new SecurityMetaData class and adding as an attachment to the DeploymentUnit. > If this contains a ServiceName for a security domain this should be used instead of any local mapping in the subsystem, additionally the presence of this domain should act as a flag to enable the Elytron form of interceptors. > Also if an Elytron SecurityDomain is selected for the deployment it's ServiceName should be set on the SecurityMetaData instance. > The use of the VirtualSecurityDomain API should also be removed as this attachment replaces it in a more generic way. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12537) Incoming RunAsPrincipal is not being propagated to an unsecured EJB

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12537?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12537: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Incoming RunAsPrincipal is not being propagated to an unsecured EJB > ------------------------------------------------------------------- > > Key: WFLY-12537 > URL: https://issues.redhat.com/browse/WFLY-12537 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Fix For: 21.0.0.Beta1 > > > This is a follow-up on WFLY-11604. When Elytron is activated, run-as-principal identity is not being propagated the same way it was for legacy. For JBEAP-9744, we updated EJBContext.getCallerPrincipal() so that when called from an unsecured bean with no incoming runas identity, an `anonymous` principal will be returned. The issue WFLY-11604 discovered that EJBContext.getCallerPrincipal is returning 'anonymous' when called on an unsecured EJB even when incoming RunAsPrincipal identity should have been propagated. This issue is to see whether this can be fixed without breaking the fix for JBEAP-9744. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11868) Documentation for Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-11868?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-11868: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Documentation for Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-11868 > URL: https://issues.redhat.com/browse/WFLY-11868 > Project: WildFly > Issue Type: Feature Request > Components: REST, Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Labels: EAP-CD19 > Fix For: 21.0.0.Beta1 > > > This feature request is about making use of authentication configuration on the client side of the REST deployment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12215) Support encrypted expression resolution using a CredentialStore

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12215?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12215: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Support encrypted expression resolution using a CredentialStore > --------------------------------------------------------------- > > Key: WFLY-12215 > URL: https://issues.redhat.com/browse/WFLY-12215 > Project: WildFly > Issue Type: Feature Request > Components: Documentation, Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13356) Add a Galleon layer for Webservices

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13356?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13356: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Add a Galleon layer for Webservices > ----------------------------------- > > Key: WFLY-13356 > URL: https://issues.redhat.com/browse/WFLY-13356 > Project: WildFly > Issue Type: Feature Request > Components: Build System, Web Services > Reporter: Brian Stansberry > Assignee: Jim Ma > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13177: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13177 > URL: https://issues.redhat.com/browse/WFLY-13177 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 13.0.0.Final, 16.0.0.Final > Reporter: Guido Jäkel > Assignee: Eduardo Martins > Priority: Critical > Fix For: 21.0.0.Beta1 > > > On WF-13 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented. > This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12945) Migrate undertow subsystem to new MSC value API

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12945?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12945: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Migrate undertow subsystem to new MSC value API > ----------------------------------------------- > > Key: WFLY-12945 > URL: https://issues.redhat.com/browse/WFLY-12945 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12765) Webservice deployment fails

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12765?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12765: ------------------------------------ Fix Version/s: 21.0.0.Beta1 (was: 20.0.0.Final) > Webservice deployment fails > --------------------------- > > Key: WFLY-12765 > URL: https://issues.redhat.com/browse/WFLY-12765 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 18.0.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Major > Fix For: 21.0.0.Beta1 > > > Enabling elytron in undertow subsystem, EAP fails to deploy a webservice war and show the following error messages: > 17:44:48,834 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "wsat-simple.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.other"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ws.endpoint.\"wsat-simple.war\".\"org.jboss.as.quickstarts.wsa > t.simple.RestaurantServiceATImpl\" is missing [jboss.security.security-domain.other]"] > } > 17:44:48,836 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "wsat-simple.war" was rolled back with the following failure message: > { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.other"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ws.endpoint.\"wsat-simple.war\".\"org.jboss.as.quickstarts.wsat.simple.RestaurantServiceATImpl\" is missing [jboss.security.security-domain.other]"] > } > 17:44:48,867 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-7) JBWS022102: Cannot stop endpoint in state UNDEFINED: jboss.ws:context=,endpoint=org.jboss.as.quickstarts.wsat.simple.RestaurantServiceATImpl -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

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 June 2020