November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1425) Add support for JASPIC / JSR-196

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1425?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1425: ---------------------------------- Fix Version/s: 1.2.0.Beta11 (was: 1.2.0.Beta10) > Add support for JASPIC / JSR-196 > -------------------------------- > > Key: ELY-1425 > URL: https://issues.jboss.org/browse/ELY-1425 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta11 > > > This is an overall tracking task for changes required to WildFly Elytron to support JASPIC. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1409) Update HTTP authentication mechanism API to support re-use of response handlers

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1409?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1409: ---------------------------------- Fix Version/s: 1.2.0.Beta11 (was: 1.2.0.Beta10) > Update HTTP authentication mechanism API to support re-use of response handlers > ------------------------------------------------------------------------------- > > Key: ELY-1409 > URL: https://issues.jboss.org/browse/ELY-1409 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta11 > > > At the moment the response handler can only access the response, it can not access anything from the request unless created with access to the request. > Making the scopes available should allow for state to be transferred on the request scope. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1405) The password attribute of resource owner credentials should support a credential store reference

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1405?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1405: ---------------------------------- Fix Version/s: 1.2.0.Beta11 (was: 1.2.0.Beta10) > The password attribute of resource owner credentials should support a credential store reference > ------------------------------------------------------------------------------------------------ > > Key: ELY-1405 > URL: https://issues.jboss.org/browse/ELY-1405 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta11 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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.Beta11 (was: 1.2.0.Beta10) > <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.Beta11 > > > 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, 5 months

1
0
0 / 0

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

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.Beta11 (was: 1.2.0.Beta10) > Add option to override the TrustManager within <authentication-client ></authentication> > ---------------------------------------------------------------------------------------- > > 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.Beta11 > > > 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 > trust managers are actually enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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.Beta11 (was: 1.2.0.Beta10) > 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.Beta11 > > > 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, 5 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.Beta11 (was: 1.2.0.Beta10) > 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.Beta11 > > > 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, 5 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.Beta11 (was: 1.2.0.Beta10) > 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 > Fix For: 1.2.0.Beta11 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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.Beta11 (was: 1.2.0.Beta10) > 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.Beta11 > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1448) API Compatibility for org.wildfly.security.mechanism.MechanismUtil

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1448?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1448: ---------------------------------- Fix Version/s: 1.2.0.Beta11 (was: 1.2.0.Beta10) > API Compatibility for org.wildfly.security.mechanism.MechanismUtil > ------------------------------------------------------------------ > > Key: ELY-1448 > URL: https://issues.jboss.org/browse/ELY-1448 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.2.0.Beta11 > > > Backwards compatibility has been broken on the public handleCallbacks methods so this needs to be fixed. > However this class should not really be a public API, it has been picked up in the package as we have the AuthenticationMechanismException which does need to be public. > The entire class should be deprecated and the impl moved to a private package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017