March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELYWEB-100) Component Upgrades

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created ELYWEB-100: ----------------------------------------- Summary: Component Upgrades Key: ELYWEB-100 URL: https://issues.redhat.com/browse/ELYWEB-100 Project: Elytron Web Issue Type: Component Upgrade Reporter: Ashley Abdel-Sayed Assignee: Darran Lofthouse - Upgrade Undertow to 2.0.30.Final - Upgrade HttpComponents:HttpClient to 4.5.12 - Upgrade WildFly Common to 1.5.4.Final - Upgrade WildFly Elytron to 1.11.2.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13252) JSF IdMapper can create repeated ids in clustered environments causing: IllegalStateException with postback

by Ricardo Martin Camarero (Jira)

Ricardo Martin Camarero created WFLY-13252: ---------------------------------------------- Summary: JSF IdMapper can create repeated ids in clustered environments causing: IllegalStateException with postback Key: WFLY-13252 URL: https://issues.redhat.com/browse/WFLY-13252 Project: WildFly Issue Type: Bug Components: JSF Affects Versions: 19.0.0.Beta3 Reporter: Ricardo Martin Camarero Assignee: Ricardo Martin Camarero In the round-robin load-balancing environment, IllegalStateException occurs with postback action. This issue seems to occur notably when set javax.faces.PARTIAL_STATE_SAVING=false. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5175) Allow to configure log levels using env. properties in HA-CEP

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5175: ------------------------------------ Summary: Allow to configure log levels using env. properties in HA-CEP Key: DROOLS-5175 URL: https://issues.redhat.com/browse/DROOLS-5175 Project: Drools Issue Type: Task Reporter: Jiri Petrlik Assignee: Jiri Petrlik Fix For: 7.35.0.Final The goal of this JIRA is to allow to configure log levels using environment properties. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12491) f:viewParam component only works for the first ajax request, but for the second ajax request and so forth the submitted value is null

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFLY-12491?page=com.atlassian.jira.plugi... ] Bartosz Spyrko commented on WFLY-12491: --------------------------------------- Resolving the issue as it was fixed in WFLY-12870 > f:viewParam component only works for the first ajax request, but for the second ajax request and so forth the submitted value is null > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12491 > URL: https://issues.redhat.com/browse/WFLY-12491 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 18.0.0.Beta1 > Environment: * JBoss EAP 7.2.3 > * Java EE 7 > Reporter: Chao Wang > Priority: Major > Labels: downstream_dependency > > I'm using the viewParam in my JSF page and it works well at first request, but when I send another request using ajax the value of viewParam is lost. This issue only happens when I use javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true. When I use javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=false it works well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5174) [Data Modeler] New field of data object throws an error

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5174?page=com.atlassian.jira.plug... ] Anna Dupliak commented on DROOLS-5174: -------------------------------------- Followed your steps but cannot reproduce it on my local 7.35. Could you reproduce it here: http://kieci-02.lab.eng.brq.redhat.com:8080/kie-docker-ui-webapp? > [Data Modeler] New field of data object throws an error > ------------------------------------------------------- > > Key: DROOLS-5174 > URL: https://issues.redhat.com/browse/DROOLS-5174 > Project: Drools > Issue Type: Bug > Affects Versions: 7.35.0.Final > Reporter: Jozef Marko > Assignee: Walter Medvedeo > Priority: Critical > Labels: Regression, drools-tools > Attachments: Screenshot from 2020-03-17 16-08-39.png > > > There is an error thrown during creation of new field of data object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1943) Upgrade WildFly Common 1.5.4.Final

by Ashley Abdel-Sayed (Jira)

Ashley Abdel-Sayed created ELY-1943: --------------------------------------- Summary: Upgrade WildFly Common 1.5.4.Final Key: ELY-1943 URL: https://issues.redhat.com/browse/ELY-1943 Project: WildFly Elytron Issue Type: Component Upgrade Reporter: Ashley Abdel-Sayed Assignee: Darran Lofthouse -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1943) Upgrade WildFly Common 1.5.4.Final

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/ELY-1943?page=com.atlassian.jira.plugin.... ] Ashley Abdel-Sayed reassigned ELY-1943: --------------------------------------- Assignee: Ashley Abdel-Sayed (was: Darran Lofthouse) > Upgrade WildFly Common 1.5.4.Final > ---------------------------------- > > Key: ELY-1943 > URL: https://issues.redhat.com/browse/ELY-1943 > Project: WildFly Elytron > Issue Type: Component Upgrade > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5174) [Data Modeler] New field of data object throws an error

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5174: ----------------------------------- Summary: [Data Modeler] New field of data object throws an error Key: DROOLS-5174 URL: https://issues.redhat.com/browse/DROOLS-5174 Project: Drools Issue Type: Bug Affects Versions: 7.35.0.Final Reporter: Jozef Marko Assignee: Walter Medvedeo Attachments: Screenshot from 2020-03-17 16-08-39.png There is an error thrown during creation of new field of data object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4871) Upgrade WildFly Elytron to 1.12.0.CR1

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4871?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4871: ------------------------------------- Summary: Upgrade WildFly Elytron to 1.12.0.CR1 (was: Upgrade WildFly Elytron to 1.11.3.Final) > Upgrade WildFly Elytron to 1.12.0.CR1 > ------------------------------------- > > Key: WFCORE-4871 > URL: https://issues.redhat.com/browse/WFCORE-4871 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Lin Gao > Assignee: Darran Lofthouse > Priority: Major > Labels: downstream_dependency > > https://github.com/wildfly-security/wildfly-elytron/compare/1.11.2.Final.... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1940) Elytron LDAP Squashes Authentication Exception

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1940?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1940: ---------------------------------- Fix Version/s: 1.12.0.CR1 > Elytron LDAP Squashes Authentication Exception > ---------------------------------------------- > > Key: ELY-1940 > URL: https://issues.redhat.com/browse/ELY-1940 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Major > Labels: downstream_dependency, elytron, ldap, logging > Fix For: 1.6.6.Final, 1.12.0.CR1 > > > Trace logging shows: > {code} > 2020-03-10 13:51:38,549 DEBUG [org.wildfly.security] (management task-1) Found entry [uid=dguthrie,ou=users,dc=example,dc=com]. > 2020-03-10 13:51:38,550 DEBUG [org.wildfly.security] (management task-1) Identity for principal [dguthrie] found at [uid=dguthrie,ou=users,dc=example,dc=com]. > 2020-03-10 13:51:38,581 DEBUG [org.wildfly.security] (management task-1) Credential direct evidence verification failed. DN: [uid=dguthrie,ou=users,dc=example,dc=com] > 2020-03-10 13:51:38,581 DEBUG [org.wildfly.security] (management task-1) Context [javax.naming.ldap.InitialLdapContext@25061db2] was closed. Connection closed or just returned to the pool. > 2020-03-10 13:51:38,581 TRACE [org.wildfly.security] (management task-1) Handling AuthenticationCompleteCallback: fail > 2020-03-10 13:51:38,582 TRACE [org.jboss.remoting.remote.server] (management task-1) Server sending authentication rejected: javax.security.sasl.SaslException: ELY05013: Authentication mechanism password not verified > {code} > > Where "Credential direct evidence verification failed. DN [uid=dguthrie,ou=users,dc=example,dc=com]" is missing the exception or even a reason. > In DirectEvidenceVerifier.java around line 102 in the Exception handler it has > {code} > log.debugf("Credential direct evidence verification failed. DN: [%s]", distinguishedName,e); > {code} > In this case, the "e" is the exception, but that parameter position is for the string formatting for which there is no token in the formatter. I believe what they meant to write was: > {code} > log.debugf(e, "Credential direct evidence verification failed. DN: [%s]", distinguishedName); > {code} > See [GitHub|https://github.com/jbossas/wildfly-elytron/blob/96c2273dc0503a23d1...] > where the first parameter is the exception. A customer is migrating from legacy to elytron, and they have been using the LDAP error codes in the log for their internal IT to help figure out why people failed login. It's also invaluable for support. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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