April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-949) Add a mechanism to assign priorities to audit events

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-949?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-949: --------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > Add a mechanism to assign priorities to audit events > ---------------------------------------------------- > > Key: ELY-949 > URL: https://issues.jboss.org/browse/ELY-949 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta41 > > > We probably want something like MatchRule but also need to think about how it will be configured. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-948) Add additional audit events

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-948?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-948: --------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > Add additional audit events > --------------------------- > > Key: ELY-948 > URL: https://issues.jboss.org/browse/ELY-948 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta41 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-947) Add our own syslog implementation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-947?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-947: --------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > Add our own syslog implementation > --------------------------------- > > Key: ELY-947 > URL: https://issues.jboss.org/browse/ELY-947 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta41 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-942) Review all method names within HTTP API

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-942?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-942: --------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > Review all method names within HTTP API > --------------------------------------- > > Key: ELY-942 > URL: https://issues.jboss.org/browse/ELY-942 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta41 > > > This is a generic HTTP authentication framework not a Servlet authentication framework so should double check the naming is consistent with regards to the HTTP specifications not Servlet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-944) Support using CallbackHandler as last resort

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-944?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-944: --------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > Support using CallbackHandler as last resort > -------------------------------------------- > > Key: ELY-944 > URL: https://issues.jboss.org/browse/ELY-944 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta41 > > > In many cases where a CallbackHandler is supplied we actually still want credentials already defined on the AuthenticationConfiguration to take priority with the CallbackHandler reserved for user interaction where we do not have a credential. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[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 updated ELY-938: --------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > 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.Beta41 > > > 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
0
0 / 0

[JBoss JIRA] (ELY-939) We need to be able to support standard KeyManager instances

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-939?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-939: --------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > We need to be able to support standard KeyManager instances > ----------------------------------------------------------- > > Key: ELY-939 > URL: https://issues.jboss.org/browse/ELY-939 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta41 > > > When using PKCS#11 we should not assume we can manipulate the private keys etc.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1112) Release WildFly Elytron 1.1.0.Beta39

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1112?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1112. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta39 > ------------------------------------ > > Key: ELY-1112 > URL: https://issues.jboss.org/browse/ELY-1112 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta39 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1109) Resolve expressions in wildfly-config.xml Elytron section

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1109?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1109: ---------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > Resolve expressions in wildfly-config.xml Elytron section > --------------------------------------------------------- > > Key: ELY-1109 > URL: https://issues.jboss.org/browse/ELY-1109 > Project: WildFly Elytron > Issue Type: Enhancement > Components: XML > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta41 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1103) Special handling for JBOSS-LOCAL-USER server side authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1103?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1103: ---------------------------------- Fix Version/s: 1.1.0.Beta41 (was: 1.1.0.Beta39) > Special handling for JBOSS-LOCAL-USER server side authentication > ---------------------------------------------------------------- > > Key: ELY-1103 > URL: https://issues.jboss.org/browse/ELY-1103 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Server, SASL > Reporter: David Lloyd > Fix For: 1.1.0.Beta41 > > > If an authentication attempt comes in using the JBOSS-LOCAL-USER mechanism with an authentication name that does not correspond to a real identity, authentication fails. In previous releases, we allowed such authentications to proceed, mapping them to a "special" identity. > With the Elytron-based authentication client and server, this occurs when a specific authentication principal is explicitly set, and that authentication principal does not correspond to a real identity on the server side. Another way to trigger this problem is to have a custom callback handler which handles NameCallback and explicitly specifies a non-existent name. Note that callback handlers which accept the suggested default name will not have this problem, nor will callback handlers which are explicitly aware of the special {{OptionalNameCallback}}. Configurations which do not specify a user name will not have this problem. > While logically it is an error condition to specify a user name that does not exist, historically we have allowed such authentications to proceed because of the privileged nature of local invocations. If we decide to continue doing so, we will need to introduce a special hook into the ServerAuthenticationContext's callback handler to detect when the local user mechanism is being used, and attempt to look up the user, and if the user is not found, fall back to the special "$local" user name. Another alternative is to produce an ad-hoc identity, however this would differ in behavior in a few key ways compared to using a fallback identity. > If we decide to reject this enhancement, then the corresponding application server tests must be updated to specify a real user name or to accept the default name that is suggested. > Note that if an authorization ID is set in the authentication request, it should be respected and the run-as authorization check should happen as per normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 April 2017