June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9023) Upgrade legacy ejb client to 3.0.0.CR2

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9023?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-9023: ------------------------------ Summary: Upgrade legacy ejb client to 3.0.0.CR2 (was: Upgrade legacy ejb client to 3.0.0.CR1) > Upgrade legacy ejb client to 3.0.0.CR2 > -------------------------------------- > > Key: WFLY-9023 > URL: https://issues.jboss.org/browse/WFLY-9023 > Project: WildFly > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3036) Upgrade JBoss Remoting to 5.0.0.CR3

by David Lloyd (JIRA)

David Lloyd created WFCORE-3036: ----------------------------------- Summary: Upgrade JBoss Remoting to 5.0.0.CR3 Key: WFCORE-3036 URL: https://issues.jboss.org/browse/WFCORE-3036 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta28 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-341) PEM file format support

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-341?page=com.atlassian.jira.plugin.sy... ] Pedro Igor commented on ELY-341: -------------------------------- Maybe we can close this one and create specific JIRAs when we found necessary. Like we had recently for private key PEM support. > PEM file format support > ----------------------- > > Key: ELY-341 > URL: https://issues.jboss.org/browse/ELY-341 > Project: WildFly Elytron > Issue Type: Enhancement > Components: KeyStores > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.2.0.Beta1 > > > We should add support for PEM formats for formats including (but not limited to): > * X.509 Certificate > * CSRs > * CRLs > * RSA and DSA Public and Private Keys > * PKCS8 format Private Keys > * DH parameters > * ECDSA Public Key > * EC Private Key > * EC Parameters > This API could be consumed by various utilities or by custom credential storage implementations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-11) Interoperability Testing

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-11?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse resolved ELY-11. --------------------------------- Resolution: Out of Date > Interoperability Testing > ------------------------ > > Key: ELY-11 > URL: https://issues.jboss.org/browse/ELY-11 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Fix For: 1.1.0.CR2 > > > This does not necessarily belong here as it may be an independent project of it's own but for now here it is. > WildFly-Elytron and WildFly-SASL are going to be used with different providers of the SPI exposed by these projects, rather than waiting until we are integrating within WildFly we should create project(s) to test the interoperability of these two projects with potential projects that will implement the SPI. > The interoperability testing will predominantly validate two areas: - > 1 - The SPIs being exposed by these project for the integration of different providers is actually valid. > 2 - The implementation and APIs of the related providers are in fact capable of meeting the requirements for WildFly. > The sooner we can identify any mis-match in this area the better to give us time to work out the solution. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-25) Authentication (and identity loading) lifecycle.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-25?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse resolved ELY-25. --------------------------------- Resolution: Out of Date > Authentication (and identity loading) lifecycle. > ------------------------------------------------ > > Key: ELY-25 > URL: https://issues.jboss.org/browse/ELY-25 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 1.1.0.CR2 > > > Just a place holder to think about this one, anything involved in the process may need to know when the current round trip finishes. > e.g. Once an LDAP connection is obtained we may want to cache it for the duration of the request which means we need to clean it up at the appropriate time. > Alternatively some form of pool may be sufficient but just raising this issue so we ensure it is covered one way or another. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-23) Add support for RFC5803

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-23?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-23: -------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.1.0.CR2) > Add support for RFC5803 > ----------------------- > > Key: ELY-23 > URL: https://issues.jboss.org/browse/ELY-23 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta1 > > > RFC5803 adds support for storing SCRAM secrets in the 'authPassword' attribute introduced by RFC3112 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-22) Expand LDAP realm to support RFC3112

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-22?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-22: -------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.1.0.CR2) > Expand LDAP realm to support RFC3112 > ------------------------------------ > > Key: ELY-22 > URL: https://issues.jboss.org/browse/ELY-22 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta1 > > > RFC3112 adds a new attribute 'authPassword' and can be used to store passwords in various formats. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-13) Interoperability testing with KeyCloak

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-13?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse resolved ELY-13. --------------------------------- Resolution: Done > Interoperability testing with KeyCloak > -------------------------------------- > > Key: ELY-13 > URL: https://issues.jboss.org/browse/ELY-13 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > 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-30) Authentication and establisment of IdentityContext as the authenticated identity.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-30?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse resolved ELY-30. --------------------------------- Resolution: Out of Date > Authentication and establisment of IdentityContext as the authenticated identity. > --------------------------------------------------------------------------------- > > Key: ELY-30 > URL: https://issues.jboss.org/browse/ELY-30 > Project: WildFly Elytron > Issue Type: Sub-task > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > 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-29) Common Use Cases

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-29?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse resolved ELY-29. --------------------------------- Resolution: Done > Common Use Cases > ---------------- > > Key: ELY-29 > URL: https://issues.jboss.org/browse/ELY-29 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.CR2 > > > The API/SPI of Elytron is based around numerous discussions on the scenarios we need to support in an application server environment - this is a parent task to start adding some test cases that cover these scenarios. > Any subsequent API evolution has to take into account the scenarios we must - this will also be key to identifying backwards compatibility going forward. -- 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