August 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-203) Add OAuth2 SASL Mechanism

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-203?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-203: --------------------------------- Fix Version/s: 2.0.0.Alpha1 > Add OAuth2 SASL Mechanism > ------------------------- > > Key: ELY-203 > URL: https://issues.jboss.org/browse/ELY-203 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 2.0.0.Alpha1 > > > See https://tools.ietf.org/html/draft-ietf-kitten-sasl-oauth-21. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-214) Add support for OpenSSL-style key and certificate files

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-214?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-214: --------------------------------- Fix Version/s: 1.0.0.Alpha5 > Add support for OpenSSL-style key and certificate files > ------------------------------------------------------- > > Key: ELY-214 > URL: https://issues.jboss.org/browse/ELY-214 > Project: WildFly Elytron > Issue Type: Enhancement > Components: KeyStores > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.0.0.Alpha5 > > > Do the following: > * Research the various supported key and cert file formats supported by OpenSSL > * Determine what the JSSE equivalent is of each, if any > * Add {{KeyStore}} support for keys of any type or format which is not supported by JSSE -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-248) Inconsistent behavior in FileSystemRealm when verifying credentials and multiple credentials are set

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-248?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-248: --------------------------------- Fix Version/s: 1.0.0.Alpha4 > Inconsistent behavior in FileSystemRealm when verifying credentials and multiple credentials are set > ---------------------------------------------------------------------------------------------------- > > Key: ELY-248 > URL: https://issues.jboss.org/browse/ELY-248 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.0.0.Alpha2 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-180) JACC backwards compatibility test in WildFly

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-180?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-180: --------------------------------- Fix Version/s: 1.0.0.Alpha5 > JACC backwards compatibility test in WildFly > -------------------------------------------- > > Key: ELY-180 > URL: https://issues.jboss.org/browse/ELY-180 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.0.0.Alpha5 > > > Check Elytron JACC against WildFly integration tests and TCK -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-181) Review JACC in Servlet and EJB subsystems

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-181?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-181: --------------------------------- Fix Version/s: 1.0.0.Alpha5 > Review JACC in Servlet and EJB subsystems > ----------------------------------------- > > Key: ELY-181 > URL: https://issues.jboss.org/browse/ELY-181 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-212) Client-side SSL context configuration is subtly wrong

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-212?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-212: --------------------------------- Fix Version/s: 1.0.0.Alpha5 > Client-side SSL context configuration is subtly wrong > ----------------------------------------------------- > > Key: ELY-212 > URL: https://issues.jboss.org/browse/ELY-212 > Project: WildFly Elytron > Issue Type: Bug > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Alpha5 > > > SSL context client-side configuration is problematic in that the SSL context is not (and cannot be) cached. This means that we lose SSL session reuse and other benefits which may cause problems for users. > However we also cannot just cache an SSL context on a configuration either - the client credentials may vary on each request, causing leakage between identities. > What we need to do is have a separate SSL context client configuration mechanism, and use the generic client context configuration to reference this SSL context client configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-221) Implement a better X.500 principal mapper

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-221?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-221: --------------------------------- Fix Version/s: 1.0.0.Alpha5 > Implement a better X.500 principal mapper > ----------------------------------------- > > Key: ELY-221 > URL: https://issues.jboss.org/browse/ELY-221 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: David Lloyd > Fix For: 1.0.0.Alpha5 > > > We can provide something better than a flat string mapping. Some thoughts on requirements: > * Require that a minimum set of keys are present, else return {{null}} > * Allow piecewise assembly of principal names with the following components: > ** Static string > ** Single attribute value e.g. {{dc[0]}} > ** Joined attribute value (with optional subrange) e.g. {{dc:"."}} would convert {{dc=example,dc=com}} to {{example.com}} > ** Joined attribute value in reverse (with optional subrange) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-211) Client-side trust store configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-211?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-211: --------------------------------- Fix Version/s: 1.0.0.Alpha5 > Client-side trust store configuration > ------------------------------------- > > Key: ELY-211 > URL: https://issues.jboss.org/browse/ELY-211 > Project: WildFly Elytron > Issue Type: Task > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Alpha5 > > > Lest I forget. The client needs the ability to supplement the default trust store, to restrict the set of acceptable peer certificates/signers, for mutual authentication purposes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-179) Implement JACC-based Authorization

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-179?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-179: --------------------------------- Fix Version/s: 1.0.0.Alpha5 > Implement JACC-based Authorization > ---------------------------------- > > Key: ELY-179 > URL: https://issues.jboss.org/browse/ELY-179 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.0.0.Alpha5 > > > Provide an initial design for Elytron's Authorization based on the Java Authorization Contract for Containers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-234) Implement SPKM-1 GSS mechanism and GSS-K7XIDASOVRG3BZSQ and GS2-DT4PIK22T6APV2PY SASL mechanisms

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-234?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-234: --------------------------------- Fix Version/s: 2.0.0.Alpha1 > Implement SPKM-1 GSS mechanism and GSS-K7XIDASOVRG3BZSQ and GS2-DT4PIK22T6APV2PY SASL mechanisms > ------------------------------------------------------------------------------------------------ > > Key: ELY-234 > URL: https://issues.jboss.org/browse/ELY-234 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: David Lloyd > Fix For: 2.0.0.Alpha1 > > > Implement the "Simple Private Key" GSSAPI mechanism. This can be done in one of two ways: > # Implement SPKM as a GSSAPI mechanism, and let the GSSAPI and GS2 SASL mechanism factories automatically pick it out. > # Implement SPKM directly in SASL as "GS2-DT4PIK22T6APV2PY" and do not provide GSSAPI support for other GSSAPI consumers. > SPKM-1 supports unilateral and mutual authentication using keys. SPKM-3 supports key-based server authentication and password-based client authentication. > Background reading: > * The Simple Public-Key GSS-API Mechanism (SPKM): https://tools.ietf.org/html/rfc2025 > * Using Generic Security Service Application Program Interface (GSS-API) Mechanisms in Simple Authentication and Security Layer (SASL): The GS2 Mechanism Family: https://tools.ietf.org/html/rfc5801 > * LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKM: https://tools.ietf.org/html/rfc2847 (also referred to as SPKM-3) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 August 2015