January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-822) Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-822?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-822: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > Move MechanismConfiguration from SecurityFactory<Credential> to CredentialSource > -------------------------------------------------------------------------------- > > Key: ELY-822 > URL: https://issues.jboss.org/browse/ELY-822 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta22 > > > This will make it consistent with client side configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-835) SecurityIdentity Automatic Outflow

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-835: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > SecurityIdentity Automatic Outflow > ---------------------------------- > > Key: ELY-835 > URL: https://issues.jboss.org/browse/ELY-835 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Fix For: 1.1.0.Beta22 > > > We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains (which it has in trusted-security-domains?) so it does not need to be manually inflowed at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-838) Ability to obtain SecurityIdentity without requiring LoginPermission

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-838?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-838: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > Ability to obtain SecurityIdentity without requiring LoginPermission > -------------------------------------------------------------------- > > Key: ELY-838 > URL: https://issues.jboss.org/browse/ELY-838 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta22 > > > Integrations such as the batch subsystem within WildFly have the requirement to re-create a previous SecurityIdentity by name using their referenced SecurityDomain, however as this identity may have been inflowed the LoginPermission can not be assumed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > 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 > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta22 > > > 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.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-853) OAuth2CredentialSource must handle BearerTokenCredential only

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-853?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-853: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > OAuth2CredentialSource must handle BearerTokenCredential only > ------------------------------------------------------------- > > Key: ELY-853 > URL: https://issues.jboss.org/browse/ELY-853 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta18 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta22 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-861) Role assignment not possible for "anonymous" identity

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-861?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-861: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > Role assignment not possible for "anonymous" identity > ----------------------------------------------------- > > Key: ELY-861 > URL: https://issues.jboss.org/browse/ELY-861 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta22 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-854) OAuth2SaslServer is missing authorization and mechanism information

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-854?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-854: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > OAuth2SaslServer is missing authorization and mechanism information > ------------------------------------------------------------------- > > Key: ELY-854 > URL: https://issues.jboss.org/browse/ELY-854 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.1.0.Beta18 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Beta22 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-873) AuthenticationClient testing without jboss-modules

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-873?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-873: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > AuthenticationClient testing without jboss-modules > -------------------------------------------------- > > Key: ELY-873 > URL: https://issues.jboss.org/browse/ELY-873 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client, Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta22 > > > Keeping AuthenticationClient usable without a dependency on JBoss Modules is the kind of thing that will be easy to break. > We should probably have a matrix of tests verifying AuthenticationClient anyway, we should then repeat the tests without JBoss Modules on the ClassPath. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-887) AuthenticationContext IPv6 Address Handling

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-887?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-887: --------------------------------- Fix Version/s: 1.1.0.Beta22 (was: 1.1.0.Beta21) > 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.Beta22 > > > 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, 3 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.Beta22 (was: 1.1.0.Beta21) > 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.Beta22 > > > 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)

9 years, 3 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 January 2017