January 2015 - jboss-jira - Jboss List Archives

[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 updated ELY-13: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > 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 > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-20) Where does OTP fit into realms?

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-20?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-20: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Where does OTP fit into realms? > ------------------------------- > > Key: ELY-20 > URL: https://issues.jboss.org/browse/ELY-20 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > Will investigate further once we have a pure LDAP impl in. > We could have an architecture where we have an LDAP server that is then referenced by an OTP server or we could have the two somehow combined into one. > There are also requirements related to marking a token as used or token invalidation after too many bad attempts - this may be handled within the OTP server but for stronger authentication mechanisms may need to be more involved otherwise this becomes another case of falling back to PLAIN / BASIC auth. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-35) Notification of outcome from authentication mechanism through to realm.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-35?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-35: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Notification of outcome from authentication mechanism through to realm. > ----------------------------------------------------------------------- > > Key: ELY-35 > URL: https://issues.jboss.org/browse/ELY-35 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > Realm implementations may want to track successful / unsuccessful calls. > Note: There may be a better way to consider this so do not take the title too literally. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-81) {crypt} passwords in Apache DS longer than 8 characters are not compatible with Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-81?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-81: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > {crypt} passwords in Apache DS longer than 8 characters are not compatible with Elytron > --------------------------------------------------------------------------------------- > > Key: ELY-81 > URL: https://issues.jboss.org/browse/ELY-81 > Project: WildFly Elytron > Issue Type: Bug > Components: Passwords, Realms > Reporter: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > I have left this out of the pull request for LDAP as this is going to require some in-depth investigation of the two implementations and how they are both interpreting passwords longer than 8 characters. > It may be there is a subtle variation in the two implementations or it may just be one has a bug. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-57) Transition to enabling mechanisms to be 'managed' in server environment.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-57?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-57: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Transition to enabling mechanisms to be 'managed' in server environment. > ------------------------------------------------------------------------ > > Key: ELY-57 > URL: https://issues.jboss.org/browse/ELY-57 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > For some mechanisms there is a fair amount of initialisation that needs to be performed each time the mechanism is used, e.g. for GSSAPI we have GSSName instances, GSSCredential instances etc... > The existing convention for SASL mechanisms is that this initialisation occurs when the mechanism is instantiated which is at the time the relevant SaslServerFactory or SaslClientFactory is called. This convention really fits with the mechanisms being used in a JSE environment but once we move to a managed environment we are not so constrained. > A few options: - > - Provide a way a mechanism can cache something it has created so if called again it can re-use it. > - Provide access to a factory / inject certain resources. > - Make the mechanism fully managed in the server, when create is called the bulk of initialisation would have already occurred and what is returned handles the bare minimum state related to an authentication attemp (client or server side). > One additional comment if we do consider something like this, some mechanisms may have items cached that once cached would never change for the lifetime of the process - for others we may have additional timeouts to consider such as Kerberos ticket expiration which may mean we want to regenerate cached resources at certain points. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-119) XInclude (or just plain inclusion) support for Elytron XML schema and/or parser

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-119?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-119: --------------------------------- Fix Version/s: 1.0.0.Beta1 > XInclude (or just plain inclusion) support for Elytron XML schema and/or parser > ------------------------------------------------------------------------------- > > Key: ELY-119 > URL: https://issues.jboss.org/browse/ELY-119 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Fix For: 1.0.0.Beta1 > > > It could be as simple as interposing a DOMSource in between the file stream and the reader, or creating a wrapper XMLStreamReader which implements the include. > But I'd prefer a solution that stacks {{org.wildfly.security.auth.XMLLocation}} instances in order to give clean and concise error messages with an "include stack trace" bundled with it. Note that this requires adding a "parent" location field to that class. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-91) Unify mechanism selection and fix the tests

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-91?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-91: -------------------------------- Fix Version/s: 1.0.0.Beta1 > Unify mechanism selection and fix the tests > ------------------------------------------- > > Key: ELY-91 > URL: https://issues.jboss.org/browse/ELY-91 > Project: WildFly Elytron > Issue Type: Task > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: 1.0.0.Beta1 > > > Unify mechanism selection and fix the tests -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-106) Add ability for configuration clients to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-106?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-106: --------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Add ability for configuration clients to create SSLContext directly from config > ------------------------------------------------------------------------------- > > Key: ELY-106 > URL: https://issues.jboss.org/browse/ELY-106 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-120) Review need for UserNameDetectionCallback, consider removal

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-120?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-120: --------------------------------- Fix Version/s: 1.0.0.Beta1 > Review need for UserNameDetectionCallback, consider removal > ----------------------------------------------------------- > > Key: ELY-120 > URL: https://issues.jboss.org/browse/ELY-120 > Project: WildFly Elytron > Issue Type: Task > Components: Callbacks > Reporter: David Lloyd > Fix For: 1.0.0.Beta1 > > > This callback had a specific genesis related to certain client-side authentication sequences where early detection of the user name could avoid the need for user interaction. We need to determine if this is still relevant. Unfortunately my notes on this subject (if there were any) were in analog format and have since been lost. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-95) Password types should generate a salt if none is given

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-95?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-95: -------------------------------- Fix Version/s: 1.0.0.Beta1 > Password types should generate a salt if none is given > ------------------------------------------------------ > > Key: ELY-95 > URL: https://issues.jboss.org/browse/ELY-95 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Passwords > Reporter: David Lloyd > Fix For: 1.0.0.Beta1 > > > Password types such as {{crypt-md5}} should be able to generate a password from a {{ClearPasswordSpec}} by generating a simple random salt. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2015