June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3035) x509-credential-mapper in ldap-realm tries to verify Subject DN even if it is not configured

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3035?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-3035: --------------------------------- Affects Version/s: 3.0.0.Beta26 > x509-credential-mapper in ldap-realm tries to verify Subject DN even if it is not configured > -------------------------------------------------------------------------------------------- > > Key: WFCORE-3035 > URL: https://issues.jboss.org/browse/WFCORE-3035 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta26 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > {{ldap-realm}} tries to verify Subject DN even if it is not configured (in optional {{subject-dn-from}} attribute). Attempt to verify Subject DN should not happen in that case. > It seems it is caused by missing check in [1]. > [1] https://github.com/wildfly/wildfly-core/blob/4e3c18e143d9093401c65745e321... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3035) x509-credential-mapper in ldap-realm tries to verify Subject DN even if it is not configured

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFCORE-3035: ------------------------------------ Summary: x509-credential-mapper in ldap-realm tries to verify Subject DN even if it is not configured Key: WFCORE-3035 URL: https://issues.jboss.org/browse/WFCORE-3035 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical {{ldap-realm}} tries to verify Subject DN even if it is not configured (in optional {{subject-dn-from}} attribute). Attempt to verify Subject DN should not happen in that case. It seems it is caused by missing check in [1]. [1] https://github.com/wildfly/wildfly-core/blob/4e3c18e143d9093401c65745e321... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9015) Unclear failure description when adding elytron policy resource

by Martin Stefanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-9015?page=com.atlassian.jira.plugin.... ] Martin Stefanko reassigned WFLY-9015: ------------------------------------- Assignee: Martin Stefanko > Unclear failure description when adding elytron policy resource > --------------------------------------------------------------- > > Key: WFLY-9015 > URL: https://issues.jboss.org/browse/WFLY-9015 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Jan Kašík > Assignee: Martin Stefanko > > When adding new Elytron policy resource, operation fails with [1]. In failure message there is missing "not" and for me, a user it is confusing since it says the policy provider which I am trying to add cannot be found... > [1] > {code} > [standalone@localhost:9990 /] /subsystem=elytron/policy=foo:add() > { > "outcome" => "failed", > "failure-description" => "Could find policy provider with name [foo]", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9033) Upgrade JMS API 2.0.0

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-9033: --------------------------------- Summary: Upgrade JMS API 2.0.0 Key: WFLY-9033 URL: https://issues.jboss.org/browse/WFLY-9033 Project: WildFly Issue Type: Component Upgrade Components: JMS Affects Versions: 10.1.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil JMS 2.0.0 API has released an errata as it introduced as a change to serialVersionUID introduced a new version API see https://java.net/projects/jms-spec/pages/JMS20RevA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-8954: ------------------------------------ Hi, I think that the first change to try, is in org.jipijapa.eclipselink.WildFlyServerPlatform (as you suggested). In WildFlyServerPlatform, instead of returning the TransactionManager instance that we currently returning, we create create a custom TransactionManager (wrapper) class that delegates most of the TransactionManager calls to the original TransactionManager instance, for the TransactionManager.getTransaction(), we would return a custom Transaction (wrapper) class that delegates most calls to the original value returned by originalTransactionManager.getTransaction(). Yes, we have two levels of wrappers here. Then, in the TransactionWrapper class, we delegate most calls to the original Transaction instance, except for the Transaction.registerSynchronization(Synchronization) call, which we will not delegate to the original Transaction instance, but instead redirect to the TransactionSynchronizationRegistry.registerSynchronization(Synchronization), so that EclipseLink will be called earlier. I'm busy with a few other things at the moment, if you would like to contribute a potential patch, I can give you ideas of how to proceed on WildFly master to recreate the bug with a small unit test change and also how to translate my above (mumbo/jumbo) notes, into a clean patch. :) I also posted to [https://javaee.groups.io/g/jpa-spec/topics] suggesting that JPA 2.2 should require all persistence providers to support use of TransactionSynchronizationRegistry.registerSynchronization. Scott > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Nuno Godinho de Matos (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Nuno Godinho de Matos commented on WFLY-8954: --------------------------------------------- Hi Scott, Can you let me know if you guys have reached a conclusion? Or if you are still studying the appropriate solution for the problem? Many thanks. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-402) The flushOnSessionInvalidation attribute is missing in the jboss-web schema and the parser

by Ivo Studensky (JIRA)

Ivo Studensky created JBMETA-402: ------------------------------------ Summary: The flushOnSessionInvalidation attribute is missing in the jboss-web schema and the parser Key: JBMETA-402 URL: https://issues.jboss.org/browse/JBMETA-402 Project: JBoss Metadata Issue Type: Bug Components: web Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 10.0.2.Final The class {{org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser}} doesn't support reading {{"flushOnSessionInvalidation"}} attribute on {{"security-domain"}} element. And also the schema files for {{jboss-web.xml}} doesn't mention this attribute. The class {{org.jboss.metadata.web.jboss.JBossWebMetaData}} contains the attribute {{flushOnSessionInvalidation}}, which comes from old JBoss versions (3.2 and 4.0). [The description|https://developer.jboss.org/wiki/CachingLoginCredentials] says: ??The jboss-web.xml security-domain element now supports a flushOnSessionInvalidation boolean attribute that when true, will flush the security-domain JAAS authentication cache for the associated user principal.?? This attribute is also supported in WildFly integration with Undertow ([look at source|https://github.com/wildfly/wildfly/blob/10.0.0.CR3/undertow/src/ma...]), but the code is never reached as the flushOnSessionInvalidation attribute value stays always *false*. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1377) Remove no longer used ReteOO implementation

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1377?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1377: ------------------------------------- Also https://github.com/kiegroup/drools/commit/b8b0e6c3a0eb08329385a6f92bfd01b... > Remove no longer used ReteOO implementation > ------------------------------------------- > > Key: DROOLS-1377 > URL: https://issues.jboss.org/browse/DROOLS-1377 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 7.0.0.Beta4 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-853) OAuth2CredentialSource must handle BearerTokenCredential only

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-853?page=com.atlassian.jira.plugin.sy... ] Pedro Igor commented on ELY-853: -------------------------------- [~darranl], we can close this one. > OAuth2CredentialSource must handle BearerTokenCredential only > ------------------------------------------------------------- > > Key: ELY-853 > URL: https://issues.jboss.org/browse/ELY-853 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta18 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-854) OAuth2SaslServer is missing authorization and mechanism information

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-854?page=com.atlassian.jira.plugin.sy... ] Pedro Igor commented on ELY-854: -------------------------------- [~darranl], I think we can also close this one. > OAuth2SaslServer is missing authorization and mechanism information > ------------------------------------------------------------------- > > Key: ELY-854 > URL: https://issues.jboss.org/browse/ELY-854 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.1.0.Beta18 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 June 2017