April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method

by Guillaume Smet (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Guillaume Smet commented on WFLY-11956: --------------------------------------- Well, as demonstrated in the attached log file, the two calls are from completely different paths. It is not a bug per se. The first call comes from: {code} javax.persistence.Persistence$PersistenceUtilImpl.isLoaded(Persistence.java:154) org.hibernate.validator.internal.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:52) org.hibernate.validator.internal.engine.resolver.CachingJPATraversableResolverForSingleValidation.lambda$isReachable$0(CachingJPATraversableResolverForSingleValidation.java:43) {code} As you have a {{@Valid}} on the property, we have to check if the value is reachable from a JPA perspective. Unfortunately, we don't have a way to easily check if an object is a possible entity so right now, for each class, we ask Hibernate ORM if the value of the property is an initialized value or some sort of lazy proxy. I will try to ask Steve if he sees a better way to do that and if we could somehow determine if the object is an entity. The second call is the validation itself, for which you obviously need the value. As for adding an additional SPI, why not but I'm not a big fan of including it in a micro release so it will have to wait for 6.1. > @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11956 > URL: https://issues.jboss.org/browse/WFLY-11956 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, REST > Affects Versions: 16.0.0.Final > Reporter: Joerg Baesner > Assignee: Ronald Sigal > Priority: Major > Attachments: logging.txt, playground.zip > > > Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_: > {code} > @Path("/validated") > public interface ValidatedJaxRsInterface { > > @GET > @Valid > @Produces(MediaType.APPLICATION_JSON) > GreetingModel getHelloGreeting(); > } > {code} > will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed. > This can be reproduced with the attached reproducer application... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1764) Get all Provider implementations moved to their own module.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1764?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1764: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > Get all Provider implementations moved to their own module. > ----------------------------------------------------------- > > Key: ELY-1764 > URL: https://issues.jboss.org/browse/ELY-1764 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Diana Vilkolakova > Priority: Blocker > Fix For: 1.9.0.CR3, 2.0.0.Alpha4 > > > Generally it was the authentication client and it's XML parser that needed to be able to load all Elytron Providers so we hard coded Provider resolution. > We have a couple of alternative options: - > # Hard code the class names in the authentication client and attempt to load 'best efforts' > # Load using ServiceLoader discovery but sort them into the correct position. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1761) Unicode normalization in SASL client breaks some non-ASCII passwords

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1761?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1761: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > Unicode normalization in SASL client breaks some non-ASCII passwords > -------------------------------------------------------------------- > > Key: ELY-1761 > URL: https://issues.jboss.org/browse/ELY-1761 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.7.0.Final > Reporter: Philippe Marschall > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR3, 2.0.0.Alpha4 > > > We have users that use U+00A8 ([diaeresis|https://en.wikipedia.org/wiki/Diaeresis_(diacritic)]) as an Active Directory password. They can not log in using the Elytron LDAP realm. Here's the sequence of events: > * PlainSaslClient.evaluateChallenge calls StringPrep.encode with the profile StringPrep.PROFILE_SASL_STORED https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * StringPrep.PROFILE_SASL_STORED ors PROFILE_SASL_QUERY which ors NORMALIZE_KC https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * StringPrep.encode then normalises using NFKC which replaces U+00A8 with U+0020 U+0308 https://github.com/wildfly-security/wildfly-elytron/blob/fd74e43caf3e7019... > * Active Directory rejects the login > We would be wiling to work on a patch but we need some guidance on the desired solution. A simple solution would be a new profile in StringPrep that doesn't normalize and is used for passwords. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1779) Make 'org.wildfly.security.password.util' public API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1779?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1779: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > Make 'org.wildfly.security.password.util' public API > ---------------------------------------------------- > > Key: ELY-1779 > URL: https://issues.jboss.org/browse/ELY-1779 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR3, 2.0.0.Alpha4 > > > This is useful for populating realms and decoding password representations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1788) Update the minimum JDK build version to 11

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1788?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1788: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > Update the minimum JDK build version to 11 > ------------------------------------------ > > Key: ELY-1788 > URL: https://issues.jboss.org/browse/ELY-1788 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > Fix For: 1.9.0.CR4, 2.0.0.Alpha4 > > > The minimum build version for the project is now JDK 11, this task is to update the jdk.min.version property to reflect that for proper enforcer warnings during the build. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1789) Add a global property for the Maven XML plugin in the tests module

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1789?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1789: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > Add a global property for the Maven XML plugin in the tests module > ------------------------------------------------------------------ > > Key: ELY-1789 > URL: https://issues.jboss.org/browse/ELY-1789 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > Fix For: 1.9.0.CR4, 2.0.0.Alpha4 > > > Currently the codehaus xml-maven-plugin property only gets defined in the tests module if the build JDK is at least JDK 9, resulting in a cryptic error message if building with a version less than JDK 9. This task is to add a global property for the plugin for the minimum JDK enforcer error message shows instead of a missing plugin version message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1786) JBoss Logging Component Upgrades

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1786?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1786: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > JBoss Logging Component Upgrades > -------------------------------- > > Key: ELY-1786 > URL: https://issues.jboss.org/browse/ELY-1786 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR4, 2.0.0.Alpha4 > > > * org.jboss.logging:jboss-logging:3.4.0.Final > * org.jboss.logging:jboss-logging-annotations:2.2.0.Final > * org.jboss.logging:jboss-logging-processor:2.2.0.Final > * org.jboss.logmanager:jboss-logmanager:2.1.10.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1787) Upgrade WildFly Common to 1.5.1.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1787?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1787: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > Upgrade WildFly Common to 1.5.1.Final > ------------------------------------- > > Key: ELY-1787 > URL: https://issues.jboss.org/browse/ELY-1787 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR4, 2.0.0.Alpha4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1796) Release WildFly Elytron 2.0.0.Alpha4

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1796?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1796. ----------------------------------- Resolution: Done > Release WildFly Elytron 2.0.0.Alpha4 > ------------------------------------ > > Key: ELY-1796 > URL: https://issues.jboss.org/browse/ELY-1796 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 2.0.0.Alpha4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1794) FORM Authentication should detect FORM submission BEFORE attempting to restore from cache.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1794?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1794: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 > FORM Authentication should detect FORM submission BEFORE attempting to restore from cache. > ------------------------------------------------------------------------------------------ > > Key: ELY-1794 > URL: https://issues.jboss.org/browse/ELY-1794 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR4, 2.0.0.Alpha4 > > > If a login FORM submission is received this should be higher priority than any previously cached identity. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 April 2019