June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-938) KeyStore in authentication client should not mandate an input source

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-938?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-938. ---------------------------------- Fix Version/s: 1.1.0.Beta53 (was: 1.1.0.Beta54) Resolution: Out of Date We have PKCS#11 support in the client. > KeyStore in authentication client should not mandate an input source > -------------------------------------------------------------------- > > Key: ELY-938 > URL: https://issues.jboss.org/browse/ELY-938 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta53 > > > Some keystores such as PKCS#11 are initialised without an InputStream. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 resolved ELY-766. ---------------------------------- Fix Version/s: 1.1.0.Beta53 (was: 1.1.0.Beta54) Resolution: Out of Date Auto outflow has been solved. > 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 > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta53 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 reassigned ELY-766: ------------------------------------ Assignee: Darran Lofthouse > 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 > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta54 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1043) CS tool must perform conversion from vault 2.0 format to CredentialStore/KeystorePasswordStore

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1043?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1043. ----------------------------------- Fix Version/s: 1.1.0.Beta53 (was: 1.1.0.Beta54) Resolution: Out of Date > CS tool must perform conversion from vault 2.0 format to CredentialStore/KeystorePasswordStore > ---------------------------------------------------------------------------------------------- > > Key: ELY-1043 > URL: https://issues.jboss.org/browse/ELY-1043 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta53 > > > CS tool must perform conversion from vault 2.0 format to CredentialStore/KeystorePasswordStore. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-936) Complete equivalent of CLIENT_CERT authentication for SASL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-936?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-936. ---------------------------------- Fix Version/s: 1.1.0.Beta53 (was: 1.1.0.Beta54) Resolution: Out of Date External authentication is now working. > Complete equivalent of CLIENT_CERT authentication for SASL > ---------------------------------------------------------- > > Key: ELY-936 > URL: https://issues.jboss.org/browse/ELY-936 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta53 > > > This will likely extend outside of Elytron but track it here first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 commented on ELY-887: -------------------------------------- [~dmlloyd] Are we happy this one is covered now? > 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.Beta54 > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1030) Move TokenSecurityRealm to org.wildfly.security.auth.realm package

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-1030?page=com.atlassian.jira.plugin.s... ] Pedro Igor commented on ELY-1030: --------------------------------- I would keep it as is. We can not make them default visibility as they can be used as an API when configuring the token realm itself. > Move TokenSecurityRealm to org.wildfly.security.auth.realm package > ------------------------------------------------------------------ > > Key: ELY-1030 > URL: https://issues.jboss.org/browse/ELY-1030 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Assignee: Pedro Igor > Priority: Critical > Fix For: 1.1.0.Beta53 > > > The LDAP and JDBC realms have their own package as they have quite a few utility and configuration classes, the token realm only has one so I don't think we really need this one to be in it'own realm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1029) Support clients that provide an optional CallbackHandler

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1029?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1029. ----------------------------------- Resolution: Out of Date Configuration is already taken into account. > Support clients that provide an optional CallbackHandler > -------------------------------------------------------- > > Key: ELY-1029 > URL: https://issues.jboss.org/browse/ELY-1029 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta53 > > > Clients such as the WildFly CLI provide a CallbackHandler implementation in case it is needed and not as a sign that it must be used, i.e. the desired outcome is that if the information required can be obtained from the configuration then authentication proceeds without interaction with the end user. > Neither the CLI or the end user should be required to be fully aware of the underlying security configuration. > This is similar to web browser HTTP authentication where there is only an interaction with the user if actually required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1030) Move TokenSecurityRealm to org.wildfly.security.auth.realm package

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1030?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1030: --------------------------------------- [~pcraveiro] do we need the validators package or could we combine into one and make them default visibility? > Move TokenSecurityRealm to org.wildfly.security.auth.realm package > ------------------------------------------------------------------ > > Key: ELY-1030 > URL: https://issues.jboss.org/browse/ELY-1030 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Assignee: Pedro Igor > Priority: Critical > Fix For: 1.1.0.Beta53 > > > The LDAP and JDBC realms have their own package as they have quite a few utility and configuration classes, the token realm only has one so I don't think we really need this one to be in it'own realm. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2101) Ensure the default configurations used by clients will be compatible with stronger authentication mechanisms

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2101?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved WFCORE-2101. -------------------------------------- Fix Version/s: 3.0.0.Beta26 (was: 3.0.0.Beta27) Resolution: Done Our default configuration now does not restrict the default mechanisms so for future servers the new legacy clients will be able to authenticate. > Ensure the default configurations used by clients will be compatible with stronger authentication mechanisms > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-2101 > URL: https://issues.jboss.org/browse/WFCORE-2101 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta26 > > > i.e. a later AS release will start to enable mechs like SCRAM, client should work without additional configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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