December 2017 - jboss-jira - Jboss List Archives

[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.Beta12 (was: 1.2.0.Beta11) > 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 > Priority: Critical > Fix For: 1.2.0.Beta12 > > > 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, 7 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: --------------------------------- Priority: Major (was: Critical) > 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 > Fix For: 1.2.0.Beta12 > > > 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, 7 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 commented on ELY-849: -------------------------------------- If we do this now we will have to consider backwards compatibility. > 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 > Fix For: 1.2.0.Beta12 > > > 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, 7 months

1
0
0 / 0

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

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1370?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1370: ---------------------------------- Summary: CachingSecurityRealm and RealmIdentityCache missing TRACE logging (was: CachingSecurityRealm and RealmIdentityCache missing TRACE loggin) > CachingSecurityRealm and RealmIdentityCache missing TRACE logging > ----------------------------------------------------------------- > > Key: ELY-1370 > URL: https://issues.jboss.org/browse/ELY-1370 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Assignee: 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, 7 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 reassigned ELY-1370: ------------------------------------- Assignee: Darran Lofthouse > 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 > Assignee: 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, 7 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 reassigned ELY-1386: ------------------------------------- Assignee: (was: Darran Lofthouse) > <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 > 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, 7 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 reassigned ELY-1405: ------------------------------------- Assignee: (was: Darran Lofthouse) > 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 > Fix For: 1.2.0.Beta11 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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: ---------------------------------- Priority: Major (was: Blocker) > 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 > Assignee: Jan Kalina > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1436) Log jdbc-realm key-mapper processing

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1436?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1436: ------------------------------------- Assignee: Darran Lofthouse > Log jdbc-realm key-mapper processing > ------------------------------------ > > Key: ELY-1436 > URL: https://issues.jboss.org/browse/ELY-1436 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Choma > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta11 > > > User reported problem with getting work jdbc_realm with bcrypt mapper. He had configured org.wildfly.security to log TRACE messages, but log does not provide any useful information regarding mapping password from DB. > In this case seems problem was in mixing base64 vs. modular crypt format. > Looking into PasswordKeyMapper there is a lot of logic and lot of steps which can get wrong. So logging some TRACE messages can hint user what is going on and what went wrong. > Also I have noticed there is unhandled exception. Please at least log some TRACE message. > {code:java|title=PasswordKeyMapper.java} > } catch (InvalidKeySpecException e) { > // fall out (unlikely but possible) > } > {code} > [1] https://developer.jboss.org/message/977727 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1456) Two same SQL queries seen during one authentication attempt

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1456?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1456: ------------------------------------- Assignee: Darran Lofthouse > Two same SQL queries seen during one authentication attempt > ------------------------------------------------------------ > > Key: ELY-1456 > URL: https://issues.jboss.org/browse/ELY-1456 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.2.0.Beta10 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta11 > > > Two same sql queries are performed on authentication attempt using jdbc-realm. > {noformat} > 2017-11-29T15:53:32.399596Z 338 Query select password from user where email = 'alberto(a)myapp.com' > 2017-11-29T15:53:32.400879Z 338 Query select role, 'Roles' from user_role_auth where email = 'alberto(a)myapp.com' > 2017-11-29T15:53:32.402531Z 338 Query select password from user where email = 'alberto(a)myapp.com' > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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