September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4668) Transaction recovery of remote ejb calls should not be using static Default AuthenticationContext

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4668?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4668: ---------------------------------------- Assignee: (was: Darran Lofthouse) > Transaction recovery of remote ejb calls should not be using static Default AuthenticationContext > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-4668 > URL: https://issues.jboss.org/browse/WFCORE-4668 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Beta9 > Reporter: Ondrej Chaloupka > Priority: Critical > > The issue WFCORE-4599 removed the `AuthenticationContext` would be static. This started to cause troubles for transaction recovery processing when remote ejb calls are invoked. > The configuration that was used earlier for server to server ejb calls[1] (used with `-Dwildfly.config.url`) stopped working. > It was possible to configure the default authentication context in the `standalone.xml` for the whole elytron subsystem (in way like [2]). But this change started to cause threads being stuck on execution of remote ejb calls in WFTC (somewhere here [3]). > Because of that the WFCORE-4659 reverted back the functionality of static global authentication context. This was rather a bit workaround as the functionality should be rather working as Stuart pointed out > {quote} > - Add an explicit config to specify the authentication context used by transaction recovery > - If this is not set fall back to the default authentication context that is used by deployments > - If none of the above are set then the auth context should be empty > {quote} > [1] > {code} > <configuration> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="jta"> > <match-abstract-type name="jta" authority="jboss"/> > </rule> > </authentication-rules> > <authentication-configurations> > <configuration name="jta"> > <sasl-mechanism-selector selector="DIGEST-MD5"/> > <providers> > <use-service-loader /> > </providers> > <set-user-name name="ejb"/> > <credentials> > <clear-password password="ejb"/> > </credentials> > <set-mechanism-realm name="ApplicationRealm" /> > </configuration> > </authentication-configurations> > </authentication-client> > </configuration> > {code} > [2] > {code} > <subsystem xmlns="urn:wildfly:elytron:8.0" final-providers="combined-providers" disallowed-providers="OracleUcrypto" default-authentication-context="jta"> > <authentication-client> > <authentication-configuration name="jta" authentication-name="ejb" realm="ApplicationRealm" sasl-mechanism-selector="DIGEST-MD5"> > <credential-reference clear-text="ejb"/> > </authentication-configuration> > <authentication-context name="jta"> > <match-rule match-abstract-type-authority="jboss" authentication-configuration="jta"/> > </authentication-context> > </authentication-client> > {code} > [3] https://github.com/wildfly/wildfly-transaction-client/blob/master/src/mai... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10255) Swagger Integration does not honor JAXB @XmlTransient annotation (and possibly more)

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10255?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-10255. ------------------------------------- Resolution: Rejected I don't see the relationship to WildFly here. If you can provide more information that shows a problem in WildFly, please feel free to reopen this. > Swagger Integration does not honor JAXB @XmlTransient annotation (and possibly more) > ------------------------------------------------------------------------------------ > > Key: WFLY-10255 > URL: https://issues.jboss.org/browse/WFLY-10255 > Project: WildFly > Issue Type: Bug > Components: JAXR (legacy; not JAX-RS) > Affects Versions: 12.0.0.Final > Reporter: Jonathan Fisher > Priority: Major > > Swagger does not honor JAXB annotations. If you mark a field on an Object as @XmlTransient, it will not be rendered in the XML or JSON output to the client. However, if will still be shown in the swagger.json. If you annotate the field with @JsonIgnore (jackson annotation), it will be omitted from the swagger.json as expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12543) Subsystem metrics are missing from microprofile-metrics JSON output

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12543?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-12543. ------------------------------------- Fix Version/s: 18.0.0.Final Resolution: Done > Subsystem metrics are missing from microprofile-metrics JSON output > ------------------------------------------------------------------- > > Key: WFLY-12543 > URL: https://issues.jboss.org/browse/WFLY-12543 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 17.0.1.Final, 18.0.0.Beta1 > Reporter: Richard DiCroce > Assignee: Jeff Mesnil > Priority: Major > Fix For: 18.0.0.Final > > > Calling /metrics with Accept = application/json results in much fewer metrics being returned than when it is called without Accept (and thus returns data in the OpenMetrics format). Specifically, all the subsystem metrics (anything affected by the prefix configured in the microprofile-metrics subsystem) are missing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12585) Upgrade Jackson2 to 2.9.10

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12585?page=com.atlassian.jira.plugin... ] Alessio Soldano reassigned WFLY-12585: -------------------------------------- Assignee: Alessio Soldano (was: Brian Stansberry) > Upgrade Jackson2 to 2.9.10 > -------------------------- > > Key: WFLY-12585 > URL: https://issues.jboss.org/browse/WFLY-12585 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Blocker > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12585) Upgrade Jackson2 to 2.9.10

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-12585: -------------------------------------- Summary: Upgrade Jackson2 to 2.9.10 Key: WFLY-12585 URL: https://issues.jboss.org/browse/WFLY-12585 Project: WildFly Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Brian Stansberry Fix For: 18.0.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4314) Enchance keystore CLI commands

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4314?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4314: ------------------------------------- Fix Version/s: (was: 10.0.0.Final) > Enchance keystore CLI commands > ------------------------------ > > Key: WFCORE-4314 > URL: https://issues.jboss.org/browse/WFCORE-4314 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2496) Functionality in WildFly to encrypt database passwords

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-2496?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2496: ------------------------------------- Fix Version/s: (was: 10.0.0.Final) > Functionality in WildFly to encrypt database passwords > ------------------------------------------------------ > > Key: WFCORE-2496 > URL: https://issues.jboss.org/browse/WFCORE-2496 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Carlton Zachary > Assignee: Farah Juma > Priority: Major > > Is it possible to add functionality to WildFly to encrypt a data source password when the data source is being created? Currently WildFly/EAP stores the password as plain text in the domain.xml/standalone.xml. > Thanks -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AG-125) Initial-size limited by max-size

by Luis Barreiro (Jira)

Luis Barreiro created AG-125: -------------------------------- Summary: Initial-size limited by max-size Key: AG-125 URL: https://issues.jboss.org/browse/AG-125 Project: Agroal Issue Type: Bug Components: pool Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 1.6 The initial size of the pool is not bound to min / max, but when it's greater than max an insufficient number of connections is initialized. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AG-125) Initial-size limited by max-size

by Luis Barreiro (Jira)

[ https://issues.jboss.org/browse/AG-125?page=com.atlassian.jira.plugin.sys... ] Luis Barreiro resolved AG-125. ------------------------------ Resolution: Done > Initial-size limited by max-size > -------------------------------- > > Key: AG-125 > URL: https://issues.jboss.org/browse/AG-125 > Project: Agroal > Issue Type: Bug > Components: pool > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.6 > > > The initial size of the pool is not bound to min / max, but when it's greater than max an insufficient number of connections is initialized. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4383) DMN DT exec model does not cascade down allowedValues to input/outputValues of DT

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4383?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-4383: ----------------------------------- Labels: good-first-issue (was: ) > DMN DT exec model does not cascade down allowedValues to input/outputValues of DT > --------------------------------------------------------------------------------- > > Key: DROOLS-4383 > URL: https://issues.jboss.org/browse/DROOLS-4383 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Labels: good-first-issue > > See [DROOLS-4379] test case a. To be investigated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 10 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 September 2019