July 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-250) Release WildFly Elytron 1.0.0.Alpha3

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-250: ------------------------------------ Summary: Release WildFly Elytron 1.0.0.Alpha3 Key: ELY-250 URL: https://issues.jboss.org/browse/ELY-250 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-227) Add attribute mapping to Jdbc Security Realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-227?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-227: --------------------------------- Fix Version/s: 1.0.0.Alpha3 > Add attribute mapping to Jdbc Security Realm > -------------------------------------------- > > Key: ELY-227 > URL: https://issues.jboss.org/browse/ELY-227 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Affects Versions: 1.0.0.Alpha1 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4763) Include org.jboss.invocation in group ids that are synced to Maven central

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-4763?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-4763: ------------------------------------ [~pgier] Paul, sorry to pester, but any chance this could be looked into? > Include org.jboss.invocation in group ids that are synced to Maven central > -------------------------------------------------------------------------- > > Key: WFLY-4763 > URL: https://issues.jboss.org/browse/WFLY-4763 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: jaikiran pai > Assignee: Paul Gier > > The jboss-invocation module under the org.jboss.invocation group (https://github.com/jbossas/jboss-invocation/ - project home) isn't available in Maven central unlike most of the other org.jboss projects. > jboss-invocation is part of WildFly dependencies. Please include the org.jboss.invocation group id in the groups that are synced to Maven central. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-223) Add tests for the filesystem-backed realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-223?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-223: --------------------------------- Fix Version/s: 1.0.0.Alpha3 > Add tests for the filesystem-backed realm > ----------------------------------------- > > Key: ELY-223 > URL: https://issues.jboss.org/browse/ELY-223 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Affects Versions: 1.0.0.Alpha2 > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.0.0.Alpha3 > > > The FS-backed realm needs some test cases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-33) Identity Loading

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-33?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse reassigned ELY-33: ----------------------------------- Assignee: Darran Lofthouse > Identity Loading > ---------------- > > Key: ELY-33 > URL: https://issues.jboss.org/browse/ELY-33 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha3 > > > We currently have identity loading tied into the realm with the 'createSecurityIdentity' call, a couple of things to think about. > Security identity loading can be tied to realm impl or could be separate, identity loading could be common to many realms - maybe a subsystem concern rather than core of Elytron but just raising here for further consideration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-33) Identity Loading

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-33?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse resolved ELY-33. --------------------------------- Resolution: Out of Date The APIs have evolved quite a bit in this area, we will address further issues as they arise. > Identity Loading > ---------------- > > Key: ELY-33 > URL: https://issues.jboss.org/browse/ELY-33 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha3 > > > We currently have identity loading tied into the realm with the 'createSecurityIdentity' call, a couple of things to think about. > Security identity loading can be tied to realm impl or could be separate, identity loading could be common to many realms - maybe a subsystem concern rather than core of Elytron but just raising here for further consideration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-175) SASL mechanism availability should take into account credential support.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-175?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-175. ---------------------------------- Resolution: Done > SASL mechanism availability should take into account credential support. > ------------------------------------------------------------------------ > > Key: ELY-175 > URL: https://issues.jboss.org/browse/ELY-175 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Alpha3 > > > One of the main reasons for having a getCredentialSupport API is so that we select appropriate authentication mechanisms based on the credentials available to us or the level of validation possible. > This should also consider advertising all variants of a mechanism or strongest only. > I will mention it here but we may want as a separate task some form of downgrade detection as this could be a sign of a malicious MITM. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-197) Add mechanism selection policies to the security domains.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-197?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-197. ---------------------------------- Resolution: Done > Add mechanism selection policies to the security domains. > --------------------------------------------------------- > > Key: ELY-197 > URL: https://issues.jboss.org/browse/ELY-197 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP, SASL > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Alpha3 > > > The security domains need to be handling mechanism selection policies so that the available mechanisms can be filtered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-175) SASL mechanism availability should take into account credential support.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-175?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-175: ------------------------------------ Assignee: David Lloyd > SASL mechanism availability should take into account credential support. > ------------------------------------------------------------------------ > > Key: ELY-175 > URL: https://issues.jboss.org/browse/ELY-175 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Alpha3 > > > One of the main reasons for having a getCredentialSupport API is so that we select appropriate authentication mechanisms based on the credentials available to us or the level of validation possible. > This should also consider advertising all variants of a mechanism or strongest only. > I will mention it here but we may want as a separate task some form of downgrade detection as this could be a sign of a malicious MITM. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-197) Add mechanism selection policies to the security domains.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-197?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-197: ------------------------------------ Assignee: David Lloyd (was: Darran Lofthouse) > Add mechanism selection policies to the security domains. > --------------------------------------------------------- > > Key: ELY-197 > URL: https://issues.jboss.org/browse/ELY-197 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP, SASL > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Alpha3 > > > The security domains need to be handling mechanism selection policies so that the available mechanisms can be filtered. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015