February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-774) KeystorePasswordStore needs to be optionally passed a Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-774?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-774: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > KeystorePasswordStore needs to be optionally passed a Supplier<Provider[]> > -------------------------------------------------------------------------- > > Key: ELY-774 > URL: https://issues.jboss.org/browse/ELY-774 > Project: WildFly Elytron > Issue Type: Task > Components: Credential Store > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Fix For: 1.1.0.Beta27 > > > The current implementation assumes it is globally registered but we may want a configuration without global registration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-770) Review SASL mechanism handling of isComplete()

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-770?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-770: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > Review SASL mechanism handling of isComplete() > ---------------------------------------------- > > Key: ELY-770 > URL: https://issues.jboss.org/browse/ELY-770 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta27 > > > The javadoc of the isComplete() method states: - > _Determines whether the authentication exchange has completed. This method is typically called after each invocation of evaluateResponse() to determine whether the authentication has completed successfully or should be continued._ > Also getAuthorizationID() states: - > _Reports the authorization ID in effect for the client of this session. This method can only be called if isComplete() returns true. > _ > Although the former is very vague there just seem to be a suggestion that complete means successfully complete, our mechs are setting complete very early and other wrappers such as AuthenticationCompleteCallbackSaslServerFactory are using complete as a flag to report failures. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-822) Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-822?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-822: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource > -------------------------------------------------------------------------------- > > Key: ELY-822 > URL: https://issues.jboss.org/browse/ELY-822 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta27 > > > This will make it consistent with client side configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-766) It should be possible for domains to be configured with a list of other domains to proactively outflow to.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-766?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-766: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > It should be possible for domains to be configured with a list of other domains to proactively outflow to. > ---------------------------------------------------------------------------------------------------------- > > Key: ELY-766 > URL: https://issues.jboss.org/browse/ELY-766 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta27 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-930) Support appending a CallbackHandler to the CredentialSources

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-930?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-930: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > Support appending a CallbackHandler to the CredentialSources > ------------------------------------------------------------ > > Key: ELY-930 > URL: https://issues.jboss.org/browse/ELY-930 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta27 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-929) AuthenticationConfiguration uniqueness enhancements

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-929?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-929: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > AuthenticationConfiguration uniqueness enhancements > --------------------------------------------------- > > Key: ELY-929 > URL: https://issues.jboss.org/browse/ELY-929 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta27 > > > Apply some enhancements to AuthenticationConfiguration uniqueness. > * Add admonishing JavaDoc to {{useCallbackHandler}} to point out the importance of per-identity uniqueness of the callback handler > The following also may be possible and useful: > * Modify the {{AuthenticationConfiguration}} process to capture instances for {{Supplier}}-driven components at the time the configuration is used via the {{AuthenticationContextConfigurationClient}} > * Add a variation of {{useCallbackHandler}} which accepts a {{Supplier<CallbackHandler>}}, or a {{Function<T, CallbackHandler}} and a {{T}}, allowing constructor refs to be given -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-926) PKCS#12 support in CredentialStore with JDK-8005408

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-926?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-926: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > PKCS#12 support in CredentialStore with JDK-8005408 > --------------------------------------------------- > > Key: ELY-926 > URL: https://issues.jboss.org/browse/ELY-926 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Environment: JDK with JDK-8005408 > Reporter: Zoran Regvart > Assignee: Zoran Regvart > Priority: Minor > Fix For: 1.1.0.Beta27 > > > JDK with [JDK-8005408|http://bugs.java.com/view_bug.do?bug_id=8005408] changed the behaviour of PKCS#12 KeyStore so it will use SecretKeyFactory to convert from SecretKeySpec to SecretKey. So a SecretKeyFactorySpi implementation is needed to support PKCS#7 Data OID used when storing data as SecretKeys in the PKCS#12 KeyStore. > This relates to ELY-920 and the test failure on JDK 1.8.0_74. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-887) AuthenticationContext IPv6 Address Handling

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-887?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-887: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > AuthenticationContext IPv6 Address Handling > ------------------------------------------- > > Key: ELY-887 > URL: https://issues.jboss.org/browse/ELY-887 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta27 > > > Within authentication client we need to ensure we are handling IPv6 addresses correctly. > Especially considering an equivalent IPv6 address can have more than one String representation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-861) Role assignment not possible for "anonymous" identity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-861?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-861: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > Role assignment not possible for "anonymous" identity > ----------------------------------------------------- > > Key: ELY-861 > URL: https://issues.jboss.org/browse/ELY-861 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta27 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-889) Add a filtering RoleMapper implementation.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-889?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-889: --------------------------------- Fix Version/s: 1.1.0.Beta27 (was: 1.1.0.Beta26) > Add a filtering RoleMapper implementation. > ------------------------------------------ > > Key: ELY-889 > URL: https://issues.jboss.org/browse/ELY-889 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta27 > > > The RoleMapper APIs are built around querying one role at a time, however at times it may be desirable to obtain a set of roles an identity is a member of. > To avoid iterating every role which depending on the configuration could be thousands backed by a remote store we should have a FilteringRoleMapper implementation that will allow any checks and iteration of the roles to be restricted to a finite set of acceptable roles. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 February 2017