September 2018 - jboss-jira - Jboss List Archives

by Justin Cook (JIRA)

[ https://issues.jboss.org/browse/ELY-1653?page=com.atlassian.jira.plugin.s... ] Justin Cook commented on ELY-1653: ---------------------------------- [~dlofthouse] There is still the issue with Javadocs on JDK10/11 but otherwise I think everything is done until there is a replacement available for sun.misc > JDK 11 Support > -------------- > > Key: ELY-1653 > URL: https://issues.jboss.org/browse/ELY-1653 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Justin Cook > Fix For: 1.7.0.CR2 > > > I suspect this will likely take three / four steps: - > # Convert he project to a multi-release built using Java 9 > # Eliminate the use of APIs in sun.misc and sun.reflect in the Java 9 variant > # Ensure the project can be build on JDK 11 > This final step may not be achievable in the short term until we can drop support for JDK 8 but by moving to the Java 9 MR jar our jar should be compatible on Java 10 and 11 as well. We may want to define a PR run that builds on Java 9 but tests in Java 11, this would mean the testsuite at least needs to be buildable on Java 11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1657) Ensure whole project buildable on JDK 11

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1657?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1657. ----------------------------------- Resolution: Done Done - CI is now fully running. > Ensure whole project buildable on JDK 11 > ---------------------------------------- > > Key: ELY-1657 > URL: https://issues.jboss.org/browse/ELY-1657 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.7.0.CR2 > > > This may be blocked on when we can remove support for Java 8 - although we could consider a build with Java 11 to exclude the Java 8 classes if that is possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1656) Ensure testsuite alone can be built and executed on Java 11

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1656?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1656. ----------------------------------- Resolution: Won't Do Marking as wont do - our CI strategy is now to build with the latest and test with the prior supported versions so we will not need to build just the testsuite with 11 until we support 12. > Ensure testsuite alone can be built and executed on Java 11 > ----------------------------------------------------------- > > Key: ELY-1656 > URL: https://issues.jboss.org/browse/ELY-1656 > Project: WildFly Elytron > Issue Type: Task > Components: Build, Testsuite > Reporter: Darran Lofthouse > Fix For: 1.7.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1657) Ensure whole project buildable on JDK 11

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1657?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1657: ------------------------------------- Assignee: Darran Lofthouse > Ensure whole project buildable on JDK 11 > ---------------------------------------- > > Key: ELY-1657 > URL: https://issues.jboss.org/browse/ELY-1657 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.7.0.CR2 > > > This may be blocked on when we can remove support for Java 8 - although we could consider a build with Java 11 to exclude the Java 8 classes if that is possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1653) JDK 11 Support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1653?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1653: ------------------------------------- Assignee: Justin Cook > JDK 11 Support > -------------- > > Key: ELY-1653 > URL: https://issues.jboss.org/browse/ELY-1653 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Justin Cook > Fix For: 1.7.0.CR2 > > > I suspect this will likely take three / four steps: - > # Convert he project to a multi-release built using Java 9 > # Eliminate the use of APIs in sun.misc and sun.reflect in the Java 9 variant > # Ensure the project can be build on JDK 11 > This final step may not be achievable in the short term until we can drop support for JDK 8 but by moving to the Java 9 MR jar our jar should be compatible on Java 10 and 11 as well. We may want to define a PR run that builds on Java 9 but tests in Java 11, this would mean the testsuite at least needs to be buildable on Java 11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1653) JDK 11 Support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1653?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1653: --------------------------------------- [~jucook] Is there anything left now? I think we are ready for Java 11 and can likely close this one. > JDK 11 Support > -------------- > > Key: ELY-1653 > URL: https://issues.jboss.org/browse/ELY-1653 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Justin Cook > Fix For: 1.7.0.CR2 > > > I suspect this will likely take three / four steps: - > # Convert he project to a multi-release built using Java 9 > # Eliminate the use of APIs in sun.misc and sun.reflect in the Java 9 variant > # Ensure the project can be build on JDK 11 > This final step may not be achievable in the short term until we can drop support for JDK 8 but by moving to the Java 9 MR jar our jar should be compatible on Java 10 and 11 as well. We may want to define a PR run that builds on Java 9 but tests in Java 11, this would mean the testsuite at least needs to be buildable on Java 11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1655) Provide Java 9 Implementation avoiding sun.reflect and sun.misc classes

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1655?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1655: ------------------------------------- Assignee: Justin Cook > Provide Java 9 Implementation avoiding sun.reflect and sun.misc classes > ----------------------------------------------------------------------- > > Key: ELY-1655 > URL: https://issues.jboss.org/browse/ELY-1655 > Project: WildFly Elytron > Issue Type: Task > Components: Security Manager > Reporter: Darran Lofthouse > Assignee: Justin Cook > Fix For: 1.7.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1597) Identity Restoration where the Principal is not quite enough.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1597?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1597: ---------------------------------- Fix Version/s: (was: 1.7.0.CR2) > Identity Restoration where the Principal is not quite enough. > ------------------------------------------------------------- > > Key: ELY-1597 > URL: https://issues.jboss.org/browse/ELY-1597 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Priority: Critical > > Presently our authentication process is build around a SecurityRealm being able to create a RealmIdentity which we then convert to an AuthorizationIdentity which is then converted to a SecurityIdentity after applying appropriate SecurityDomain configured mappings. > Generally in a SecurityRealm one of two different methods tend to be used to create the RealmIdentity. > {code:java} > RealmIdentity getRealmIdentity(Principal principal) throws RealmUnavailableException > {code} > or > {code:java} > RealmIdentity getRealmIdentity(Evidence evidence) throws RealmUnavailableException > {code} > Generally from the realms we know about, where the Principal form of the method is used the realm will likely load the attributes that go into the AuthorizationIdentity from another source, however for the form that takes Evidence often the attributes can be derived from the evidence. > Where we persist identities to be restored later such as identity propagation, batch, clustering etc we persist the name of the identity and use it to restore the identity using the Principal form of the above methods. For cases where an identity was originally created using evidence we no longer have sufficient information to recreate the identity. > This Enhancement is to review how we can address this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1525: ------------------------------------- Assignee: Darran Lofthouse > When SSO is enabled, multipart form and form enconding stop working. > -------------------------------------------------------------------- > > Key: ELY-1525 > URL: https://issues.jboss.org/browse/ELY-1525 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.6.Final, 1.2.1.Final > Reporter: Estevão Freitas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.7.0.CR2 > > > I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ". > I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On . > When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working. > If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1427) Credential store type PKCS12 works fine when using OracleJDK and OpenJDK but doesn't work using IBM JDK.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1427?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1427. ----------------------------------- Resolution: Rejected Rejected as this is not supportable. > Credential store type PKCS12 works fine when using OracleJDK and OpenJDK but doesn't work using IBM JDK. > -------------------------------------------------------------------------------------------------------- > > Key: ELY-1427 > URL: https://issues.jboss.org/browse/ELY-1427 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Priority: Critical > Fix For: 1.7.0.CR2 > > > Credential store type PKCS12 works fine when using OracleJDK and OpenJDK. > Problem occurs when we use IBM JDK, add-alias works fine for first time, but for add-alias for second time with same alias name we expect message about duplicity rather than current error message about SecretKeyFactory not availability. > {code} > "WFLYCTL0158: Operation handler failed: java.lang.RuntimeException: WFLYELY00009: Unable to complete operation. 'ELY09504: Cannot acquire a credential from the credential store->Get Key failed: 1.2.840.113549.1.7.1 SecretKeyFactory not available->1.2.840.113549.1.7.1 SecretKeyFactory not available'", > {code} > *NOTE* > I met same problem with Oracle JDK 1.8 u66, with u144 is everythink ok. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 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 2018