April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1745) The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1745?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1745: ---------------------------------- Fix Version/s: 1.9.0.CR5 (was: 1.9.0.CR4) > The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1745 > URL: https://issues.jboss.org/browse/ELY-1745 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Justin Cook > Priority: Major > Fix For: 1.9.0.CR5 > > > The NPE is due to the following code: - > {noformat} > } else if (callback instanceof AvailableRealmsCallback) { > Collection<String> names = stateRef.get().getMechanismConfiguration().getMechanismRealmNames(); > if (log.isTraceEnabled()) { > log.tracef("Handling AvailableRealmsCallback: realms = [%s]", String.join(", ", names)); > } > if (! names.isEmpty()) { > ((AvailableRealmsCallback) callback).setRealmNames(names.toArray(new String[names.size()])); > } > handleOne(callbacks, idx + 1); > {noformat} > If mechanism configuration is mandatory this should report an appropriate error, if not it should fallback to specifying an empty list. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1744) Remove use of java.security.acl APIs

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1744?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1744: ---------------------------------- Fix Version/s: 1.9.0.CR5 (was: 1.9.0.CR4) > Remove use of java.security.acl APIs > ------------------------------------ > > Key: ELY-1744 > URL: https://issues.jboss.org/browse/ELY-1744 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.9.0.CR5 > > > The 'java.security.acls' packages has been deprecated and flagged for removal, this will be removed in Java 13 > https://bugs.openjdk.java.net/browse/JDK-8191138 > Within WildFly Elytron we only seem to use it in the JAAS security realm which I don't believe is used although likely is public API. I believe the use was to mirror some PicketBox behaviour. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1742) Clean up the 'wildfly-elytron-x500-cert' module as it currently contains both public and private API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1742?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1742: ---------------------------------- Fix Version/s: 1.9.0.CR5 (was: 1.9.0.CR4) > Clean up the 'wildfly-elytron-x500-cert' module as it currently contains both public and private API > ---------------------------------------------------------------------------------------------------- > > Key: ELY-1742 > URL: https://issues.jboss.org/browse/ELY-1742 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.9.0.CR5, 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-1741) Clean up the 'wildfly-elytron-x500' module as it currently contains both public and private API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1741?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1741: ---------------------------------- Fix Version/s: 1.9.0.CR5 (was: 1.9.0.CR4) > Clean up the 'wildfly-elytron-x500' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1741 > URL: https://issues.jboss.org/browse/ELY-1741 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.9.0.CR5, 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-1766) Review relevence of webauth with Elytron authentication

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1766?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1766: ---------------------------------- Fix Version/s: 1.9.0.CR5 (was: 1.9.0.CR4) > Review relevence of webauth with Elytron authentication > ------------------------------------------------------- > > Key: ELY-1766 > URL: https://issues.jboss.org/browse/ELY-1766 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.9.0.CR5 > > > Does this just make sense in IDM / SSO environments or does it make sense for direct authentication to a server. > https://www.w3.org/TR/webauthn/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1765) Review authentication client dependencies on credential sources

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1765?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1765: ---------------------------------- Fix Version/s: 1.9.0.CR5 (was: 1.9.0.CR4) > Review authentication client dependencies on credential sources > --------------------------------------------------------------- > > Key: ELY-1765 > URL: https://issues.jboss.org/browse/ELY-1765 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.9.0.CR5 > > > Could these credential sources be discoverable from java.security.Provider with a more generic configuration API? This could help break any dependency from authentication client to the implementation. > _In the opposite direction I think it is Ok for the impl to depend on the client._ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1762) Ensure JAPICMP Compatibility and enable plug-in for all builds.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1762?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1762: ---------------------------------- Fix Version/s: 1.9.0.CR5 (was: 1.9.0.CR4) > Ensure JAPICMP Compatibility and enable plug-in for all builds. > --------------------------------------------------------------- > > Key: ELY-1762 > URL: https://issues.jboss.org/browse/ELY-1762 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.9.0.CR5 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1795) Release WildFly Elytron 1.9.0.CR4

by Darran Lofthouse (Jira)

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

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5838) Use WildFly thread pools in Artemis

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-5838?page=com.atlassian.jira.plugin.... ] Emmanuel Hugonnet reassigned WFLY-5838: --------------------------------------- Assignee: Emmanuel Hugonnet (was: Jeff Mesnil) > Use WildFly thread pools in Artemis > ----------------------------------- > > Key: WFLY-5838 > URL: https://issues.jboss.org/browse/WFLY-5838 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Jeff Mesnil > Assignee: Emmanuel Hugonnet > Priority: Major > > Artemis provides a feature to inject its executor and scheduled executor services when a ArtemisServer is created. > WildFly could leverage that to inject these services so that their thread pools are managed by WildFly. > We would have total control on the creation and configuration of these thread pools using the org.boss.as.threads extension. > The messaging-activemq extension would be updated so that a server resource would have new children using resource definitions from the org.boss.as.threads extension to configure their pools. > {noformat} > * server > * bounded-queue-thread-pool or unbounded-queue-thread-pool -> for executor service > * scheduled-thread-pool -> for scheduled executor service > {noformat} > Note that this RFE would not impact the Artemis RA that does not provide such executor injection. This will be covered by another JIRA issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1795) Release WildFly Elytron 1.9.0.CR4

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1795: ------------------------------------- Summary: Release WildFly Elytron 1.9.0.CR4 Key: ELY-1795 URL: https://issues.jboss.org/browse/ELY-1795 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.0.CR4 -- 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