March 2019 - jboss-jira - Jboss List Archives

[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.CR3 (was: 1.9.0.CR2) > 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.CR3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1749) Code review of WildFlyElytronProvider

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1749?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1749: ---------------------------------- Fix Version/s: 1.9.0.CR3 (was: 1.9.0.CR2) > Code review of WildFlyElytronProvider > ------------------------------------- > > Key: ELY-1749 > URL: https://issues.jboss.org/browse/ELY-1749 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.9.0.CR3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[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.CR3 (was: 1.9.0.CR2) > 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.CR3 > > > 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, 1 month

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.CR3 (was: 1.9.0.CR2) > 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.CR3 > > > 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, 1 month

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.CR3 (was: 1.9.0.CR2) > 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.CR3, 2.0.0.Alpha3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1773) Upgrade WildFly Common to 1.5.0.Final

by Darran Lofthouse (Jira)

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

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1775) Release WildFly Elytron 1.9.0.CR2

by Darran Lofthouse (Jira)

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

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1776) Release WildFly Elytron 2.0.0.Alpha3

by Darran Lofthouse (Jira)

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

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1774) WildFlyElytronHttpBearerProvider references the mechanism instead of it's factory

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1774?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1774. ----------------------------------- Resolution: Done > WildFlyElytronHttpBearerProvider references the mechanism instead of it's factory > --------------------------------------------------------------------------------- > > Key: ELY-1774 > URL: https://issues.jboss.org/browse/ELY-1774 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.9.0.CR2 > > > This means the mechanism is unavailable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-605) Establish Central CI Jenkins Master For Kiali

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-605?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-605: ------------------------------------ New jenkins instrance: https://kiali-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/manage Use LDAP credentials for login > Establish Central CI Jenkins Master For Kiali > --------------------------------------------- > > Key: SWSQE-605 > URL: https://issues.jboss.org/browse/SWSQE-605 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > Labels: infrastructure > > Our team at one time was allocated a Central CI Jenkins Master. > Therefore, one of the following, > Either: > a) Confirm that our team's Central CI Jenkins Master is still available and usable > Or > b) Establish a new Central CI Jenkins Master > We also need to confirm that Jenkins master in Central Ci will fit our needs like: > * is it possible to run smee.io client there to consume github events > * is it possible to install plugins we are using > * check SLA > * check backups, upgrades > * do we want to share it with istio qe team? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2019