October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1385) Add option to override the KeyManager and TrustManager within <authentication-client />

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1385?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1385: ---------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > Add option to override the KeyManager and TrustManager within <authentication-client /> > --------------------------------------------------------------------------------------- > > Key: ELY-1385 > URL: https://issues.jboss.org/browse/ELY-1385 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta7 > > > At the moment we can reference an alias from a KeyStore and reference a complete KeyStore for use by the TrustManager but there is not option to override which key and trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1379) KeyStore element does not support overriding Provider discovery

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1379?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1379: ---------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > KeyStore element does not support overriding Provider discovery > --------------------------------------------------------------- > > Key: ELY-1379 > URL: https://issues.jboss.org/browse/ELY-1379 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta7 > > > Additionally it doesn't take into account the default Provider discovery or the Provider definition at the root of the <authentication-configuration /> definition. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1370) CachingSecurityRealm and RealmIdentityCache missing TRACE loggin

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1370?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1370: ---------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > CachingSecurityRealm and RealmIdentityCache missing TRACE loggin > ---------------------------------------------------------------- > > Key: ELY-1370 > URL: https://issues.jboss.org/browse/ELY-1370 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Fix For: 1.2.0.Beta7 > > > Where caching is in use there is no TRACE logging showing the activity in the cache. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1170: ---------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]> > ----------------------------------------------------------------------------------- > > Key: ELY-1170 > URL: https://issues.jboss.org/browse/ELY-1170 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta7 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-849: --------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > Rename setMechanismProperties to setSaslMechanismProperties > ----------------------------------------------------------- > > Key: ELY-849 > URL: https://issues.jboss.org/browse/ELY-849 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta7 > > > If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties. > We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1398) Verify public API signatures during build.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1398?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1398: ---------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > Verify public API signatures during build. > ------------------------------------------ > > Key: ELY-1398 > URL: https://issues.jboss.org/browse/ELY-1398 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.6.CR1, 1.2.0.Beta7 > > > This task will involve adding the ability to generate a signature for a specific version and verify them during the build - we only want this to apply to packages identified as public API. > Animal Sniffer seems a good candidate http://www.mojohaus.org/animal-sniffer/ > Generation of a signature we can likely make on-demand as we only really need that at the point we tag a release. > We would definitely want checking to run for CI PR processing but can decide if all builds should be checking with an option to disable or all disabled with an option to enable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1387) SSLContext for where authentication client resources load from a URI.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1387?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1387: ---------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > SSLContext for where authentication client resources load from a URI. > --------------------------------------------------------------------- > > Key: ELY-1387 > URL: https://issues.jboss.org/browse/ELY-1387 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta7 > > > Where resources can be loaded from a URI we may want to define an SSLContext for access to that resource so we can verify it is a trusted resource. > i.e. our local config contains internal key and trust stores but the remove destinations may change so we load the certificates and revocation lists from an internal trusted source. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1386) <certificate-revocation-list /> should also support a URI and resource in addition to path.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1386?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1386: ---------------------------------- Fix Version/s: 1.2.0.Beta7 (was: 1.2.0.Beta6) > <certificate-revocation-list /> should also support a URI and resource in addition to path. > ------------------------------------------------------------------------------------------- > > Key: ELY-1386 > URL: https://issues.jboss.org/browse/ELY-1386 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta7 > > > KeyStores can be loaded from a path, a URI, or as a resource - the certificate revocation list should be the same. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1398) Verify public API signatures during build.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1398?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1398: ---------------------------------- Fix Version/s: 1.1.6.CR1 (was: 1.1.5.Final) > Verify public API signatures during build. > ------------------------------------------ > > Key: ELY-1398 > URL: https://issues.jboss.org/browse/ELY-1398 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.6.CR1, 1.2.0.Beta6 > > > This task will involve adding the ability to generate a signature for a specific version and verify them during the build - we only want this to apply to packages identified as public API. > Animal Sniffer seems a good candidate http://www.mojohaus.org/animal-sniffer/ > Generation of a signature we can likely make on-demand as we only really need that at the point we tag a release. > We would definitely want checking to run for CI PR processing but can decide if all builds should be checking with an option to disable or all disabled with an option to enable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1031) Make the CredentialStore class final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1031?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1031: ---------------------------------- Fix Version/s: 1.1.5.CR1 (was: 1.0.5.CR1) > Make the CredentialStore class final > ------------------------------------ > > Key: ELY-1031 > URL: https://issues.jboss.org/browse/ELY-1031 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credential Store > Reporter: Darran Lofthouse > Assignee: Farah Juma > Priority: Critical > Fix For: 1.1.5.Final, 1.2.0.Beta6 > > > Unless there is a reason this has not already be done the class should probably be made final to be sure extension is not possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 9 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 October 2017