October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3832) Support hex encoding in jdbc-realm for elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3832?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3832: ---------------------------------------- Assignee: (was: Jan Kalina) > Support hex encoding in jdbc-realm for elytron > ---------------------------------------------- > > Key: WFCORE-3832 > URL: https://issues.jboss.org/browse/WFCORE-3832 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 5.0.0.Alpha7 > Reporter: Jan Kalina > Labels: elytron > > Old database login-module can be configured passing the attribute {{hashEncoding}}, for example: > {code:xml} > <login-module code="Database" flag="required"> > <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/> > <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/> > <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/> > <module-option name="hashAlgorithm" value="SHA-1"/> > <module-option name="hashEncoding" value="hex"/> > <module-option name="hashCharset" value="UTF-8"/> > </login-module> > {code} > Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron. > Think also about the charset attribute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-414) Add tests to cover iiop configuration paarsing

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created JBMETA-414: ---------------------------------------- Summary: Add tests to cover iiop configuration paarsing Key: JBMETA-414 URL: https://issues.jboss.org/browse/JBMETA-414 Project: JBoss Metadata Issue Type: Enhancement Components: ejb Affects Versions: 12.0.0.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor Add test to cover the old way of parsing iiop configuration (even if this doesn't follow the schemas) @see https://github.com/wildfly/wildfly/pull/11408 and https://github.com/wildfly/wildfly/pull/11700 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3947) Support SSL Certificate revocation using OCSP

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3947?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3947: ---------------------------------------- Assignee: (was: Jan Kalina) > Support SSL Certificate revocation using OCSP > --------------------------------------------- > > Key: WFCORE-3947 > URL: https://issues.jboss.org/browse/WFCORE-3947 > Project: WildFly Core > Issue Type: Task > Components: Security > Affects Versions: 6.0.0.Alpha2 > Reporter: Jan Kalina > Priority: Critical > > - Provide undertow's client certificate revocation capability when undertow is used as a load balancer using OCSP. > (CRL capability is provided in the earlier release as part of Elytron SSL Consolidation effort that this JIRA is cloned from) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3969) ALIAS_FILTER in Elytron trustmanager ignored when crl used

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3969?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-3969: ---------------------------------------- Assignee: (was: Jan Kalina) > ALIAS_FILTER in Elytron trustmanager ignored when crl used > ---------------------------------------------------------- > > Key: WFCORE-3969 > URL: https://issues.jboss.org/browse/WFCORE-3969 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 6.0.0.Alpha2 > Reporter: Jan Kalina > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections

by Jan-Willem Gmelig Meyling (JIRA)

[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ] Jan-Willem Gmelig Meyling commented on WFLY-10531: -------------------------------------------------- I seem to suffer from this issue in WF14.0.1 too... > Wildfly leaks ActiveMQ connections > ---------------------------------- > > Key: WFLY-10531 > URL: https://issues.jboss.org/browse/WFLY-10531 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Environment: openjdk 8 / openjdk 9, Linux > Reporter: Marcel Šebek > Assignee: Jeff Mesnil > Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip > > > After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on > IJ000453: Unable to get managed connection for java:/JmsXA > and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log: > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69) > Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time. > It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-404) Consumer Job For Istio Trigger

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-404?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-404: ------------------------------- Sprint: Kiali Sprint #12 > Consumer Job For Istio Trigger > ------------------------------ > > Key: SWSQE-404 > URL: https://issues.jboss.org/browse/SWSQE-404 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Once Istio QE creates the Msg Bus Trigger, create a consumer job that will in turn run the needed Kiali jobs/tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-419) Enhance Maistra Pipeline Support

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-419?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-419: ------------------------------- Sprint: Kiali Sprint #11, Kiali Sprint #12 (was: Kiali Sprint #11) > Enhance Maistra Pipeline Support > -------------------------------- > > Key: SWSQE-419 > URL: https://issues.jboss.org/browse/SWSQE-419 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Maistra Pipeline would need to have some additions to have better support (Some of them include) > - Remove Maistra Job from Upstream Pipeline (SWSQE-423) > - Add Minimal CR option (this will install default versions listed on istio-operator) - (SWSQE-429) > > - Include Option to run or not run Kiali Istio Checker > > - Crate Maistra Message Bus Job (SWSQE-424) > - Include Bookinfo, Include E2E Test Run, Include UI Test Run (SWSQE-430) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4144) Add support for registering a single JVM / Server wide default SSLContext

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4144: ---------------------------------------- Summary: Add support for registering a single JVM / Server wide default SSLContext Key: WFCORE-4144 URL: https://issues.jboss.org/browse/WFCORE-4144 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.Alpha2 By registering a global SSLContext libraries used within the application server can make use of a managed SSLContext instead of relying on one automatically being created through the standard system properties. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11094) Elytron does not do RunAs identity remote propagation

by Teresa Miyar (JIRA)

[ https://issues.jboss.org/browse/WFLY-11094?page=com.atlassian.jira.plugin... ] Teresa Miyar moved WFCORE-4142 to WFLY-11094: --------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-11094 (was: WFCORE-4142) Component/s: Security (was: Security) > Elytron does not do RunAs identity remote propagation > ----------------------------------------------------- > > Key: WFLY-11094 > URL: https://issues.jboss.org/browse/WFLY-11094 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Teresa Miyar > Assignee: Teresa Miyar > Labels: downstream_dependency > > Elytron does not do RunAs identity remote propagation > -> EJB with @RunAs("ejbuser") -> remote EJB , where Elytron security forwarding is configured, @RunAs is not working. And caused authentication error when trying to call the 2nd server when @RunAs is added. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3058) [DMN Designer] Decision Navigator dock is shown for business process

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3058?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3058: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Decision Navigator dock is shown for business process > -------------------------------------------------------------------- > > Key: DROOLS-3058 > URL: https://issues.jboss.org/browse/DROOLS-3058 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Labels: drools-tools > Attachments: Screenshot from 2018-10-01 10-04-33.png > > > DMN model designer shows additional *Decision Navigator* dock next to *Project Explorer*. The issue is this additional dock remains opened also for business process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018