June 2017 - jboss-jira - Jboss List Archives

[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.CR2 (was: 1.1.0.CR1) > 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.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

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.CR2 (was: 1.1.0.CR1) > 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.CR2 > > > 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)

8 years, 10 months

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.CR2 (was: 1.1.0.CR1) > 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.CR2 > > > 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)

8 years, 10 months

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.CR2 (was: 1.1.0.CR1) > 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.CR2 > > > 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)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-937) SSLContext in authentication client has no trust configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-937?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-937: --------------------------------- Fix Version/s: 1.1.0.CR2 (was: 1.1.0.CR1) > SSLContext in authentication client has no trust configuration > -------------------------------------------------------------- > > Key: ELY-937 > URL: https://issues.jboss.org/browse/ELY-937 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.CR2 > > > Currently it requires on the system default so it is not possible to configure trusted certificate authorities. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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.CR2 (was: 1.1.0.CR1) > 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.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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.CR2 (was: 1.1.0.CR1) > 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.CR2 > > > 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)

8 years, 10 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.CR2 (was: 1.1.0.CR1) > 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.CR2 > > > 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)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1170: ---------------------------------- Fix Version/s: 1.1.0.CR2 (was: 1.1.0.CR1) > The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]> > ----------------------------------------------------------------------------------- > > Key: ELY-1170 > URL: https://issues.jboss.org/browse/ELY-1170 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1099) User client callback should be used for all unrecognized callback types

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1099?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1099: ---------------------------------- Fix Version/s: 1.1.0.CR2 (was: 1.1.0.CR1) > User client callback should be used for all unrecognized callback types > ----------------------------------------------------------------------- > > Key: ELY-1099 > URL: https://issues.jboss.org/browse/ELY-1099 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.CR2 > > > If we have an unsupported/unknown callback type, but there's a user callback handler, we should let the user callback handler take it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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