June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-559) Token-based authentication should forward authentication

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-559?page=com.atlassian.jira.plugin.sy... ] Pedro Igor commented on ELY-559: -------------------------------- I think we can defer to version 2. > Token-based authentication should forward authentication > -------------------------------------------------------- > > Key: ELY-559 > URL: https://issues.jboss.org/browse/ELY-559 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Mechanisms > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.1.0.Beta54 > > > Mechanisms that handle BearerTokenCredetials (ELY-557) should forward them as public or private credentials (ELY-473 / https://github.com/wildfly-security/wildfly-elytron/pull/434 ). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-639) SecurityIdentity and PeerIdentity should have more runAs* variants

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-639?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-639: --------------------------------- Fix Version/s: 2.0.0.Alpha1 (was: 1.1.0.Beta54) > SecurityIdentity and PeerIdentity should have more runAs* variants > ------------------------------------------------------------------ > > Key: ELY-639 > URL: https://issues.jboss.org/browse/ELY-639 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Fix For: 2.0.0.Alpha1 > > > The XxxIdentity classes have fewer runAs modes than (for example) Contextual objects do. Unifying these types would be ideal, but I'd settle for adding the missing types, including the {{Exception*}} functional types from WildFly Common. -- 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 David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-887?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-887: --------------------------------- Yeah I think so. > 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-565) A first boot SSLContext

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-565?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-565: --------------------------------- Fix Version/s: 2.0.0.Alpha1 (was: 1.1.0.Beta54) > A first boot SSLContext > ----------------------- > > Key: ELY-565 > URL: https://issues.jboss.org/browse/ELY-565 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SSL > Reporter: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > For developers we have a requirement to be able to provide a working SSL set up before the user configures their own keys and certificates. We will need to tie this with our other SSL related tasks for fully configures set ups but we probably are also going to require an automatic mode. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-559) Token-based authentication should forward authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-559?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-559: ------------------------------------ Assignee: Pedro Igor > Token-based authentication should forward authentication > -------------------------------------------------------- > > Key: ELY-559 > URL: https://issues.jboss.org/browse/ELY-559 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Mechanisms > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.1.0.Beta54 > > > Mechanisms that handle BearerTokenCredetials (ELY-557) should forward them as public or private credentials (ELY-473 / https://github.com/wildfly-security/wildfly-elytron/pull/434 ). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-559) Token-based authentication should forward authentication

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-559?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-559: -------------------------------------- [~pcraveiro] do we have anything for this? If not maybe defer to version 2? > Token-based authentication should forward authentication > -------------------------------------------------------- > > Key: ELY-559 > URL: https://issues.jboss.org/browse/ELY-559 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Mechanisms > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.1.0.Beta54 > > > Mechanisms that handle BearerTokenCredetials (ELY-557) should forward them as public or private credentials (ELY-473 / https://github.com/wildfly-security/wildfly-elytron/pull/434 ). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-951) Event handling queues

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-951?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-951: --------------------------------- Fix Version/s: 2.0.0.Alpha1 (was: 1.1.0.Beta54) > Event handling queues > --------------------- > > Key: ELY-951 > URL: https://issues.jboss.org/browse/ELY-951 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > Currently audit events are handled synchronously which may be desirable to ensure events are logged. > However this does risk performance so queuing of events may also be desirable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 resolved ELY-1103. ----------------------------------- Fix Version/s: 1.1.0.Beta53 (was: 1.1.0.Beta54) Resolution: Out of Date Marking as out of date as no further changes planned. > 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.Beta53 > > > 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 month

1
0
0 / 0

[JBoss JIRA] (ELY-950) Add local audit log rotation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-950?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-950. ---------------------------------- Fix Version/s: 1.1.0.Beta53 (was: 1.1.0.Beta54) Resolution: Out of Date > Add local audit log rotation > ---------------------------- > > Key: ELY-950 > URL: https://issues.jboss.org/browse/ELY-950 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta53 > > > Could be by time, size, rotate on start-up or a combination. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-595) Ability to provide CallbackHandler and SSLContext when AuthenticationConfiguration dynamically loaded.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-595?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-595. ---------------------------------- Fix Version/s: 1.1.0.Beta53 (was: 1.1.0.Beta54) Resolution: Out of Date Apis can be used to modify the AuthenticationConfiguration and add a CallbackHandler, a custom SSLContext can be associated with the AuthenticationContext. > Ability to provide CallbackHandler and SSLContext when AuthenticationConfiguration dynamically loaded. > ------------------------------------------------------------------------------------------------------ > > Key: ELY-595 > URL: https://issues.jboss.org/browse/ELY-595 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > 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

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