July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-261) Rework (and move) UsernamePasswordHashUtil

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-261?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-261: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Rework (and move) UsernamePasswordHashUtil > ------------------------------------------ > > Key: ELY-261 > URL: https://issues.jboss.org/browse/ELY-261 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI, Passwords > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > Firstly this class is not really SASL specific so should be in a general util package. > Secondly we now have password specs and a PasswordFactory - if this class still has a future then maybe it should be using those instead of it's own custom implementation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-428) HTTP Mechanism configuration during deployment

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-428: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > HTTP Mechanism configuration during deployment > ---------------------------------------------- > > Key: ELY-428 > URL: https://issues.jboss.org/browse/ELY-428 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta8 > > > It should be possible to configure a HTTP mechanism during deployment in order to parse/load configuration and reuse it in subsequent requests to an application. > The most common use case for that is around mechanisms that need to read some configuration from inside a deployment (or provided by the mech config) when it is being deployed to the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-422) Default SSLContext?

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-422?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-422: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Default SSLContext? > ------------------- > > Key: ELY-422 > URL: https://issues.jboss.org/browse/ELY-422 > Project: WildFly Elytron > Issue Type: Task > Components: SSL > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > We know we want one, what we don't know is exactly that it means and is it an Elytron concern or subsystem concern. > One issue is within Elytron our SSLContext implementations are either server side specific or client side specific - we may even want to review if there is any way to review what it is being used for and act accordingly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-398) Authorization decisions for identity manipulation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-398?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-398: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Authorization decisions for identity manipulation > ------------------------------------------------- > > Key: ELY-398 > URL: https://issues.jboss.org/browse/ELY-398 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > We need to ensure we have appropriate permissions checks in place where one identity is manipulating another identity. > It is possible the subsystem will take a lot of the responsibility but lets start here with an issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-368) Add optional Supplier<Provider[]> to realm implementations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-368?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-368: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Add optional Supplier<Provider[]> to realm implementations > ---------------------------------------------------------- > > Key: ELY-368 > URL: https://issues.jboss.org/browse/ELY-368 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > Fix For: 1.1.0.Beta8 > > > Realms use key factories, certificate factories, password factories, etc. Most of the time they just use the default installed providers. Enhance the realms to accept an optional {{Supplier<Provider[]>}} which will be used to load these kinds of things. The default supplier should be {{Security::getProviders()}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-376) Password policies

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-376?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-376: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Password policies > ----------------- > > Key: ELY-376 > URL: https://issues.jboss.org/browse/ELY-376 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI, Passwords, Realms > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.1.0.Beta8 > > > Probably needs a design discussion first but we need to review where password policies fit in to the overall solution. > We may say that policy handling is really the responsibility of the actual realm implementation, after all items such as history are going to be very realm specific. > However there may also be a case in the generic sense that where a modifiable realm is in use a policy is desired to cover the complexity of any passwords set on that realm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-355) HTTP Authentication Mechanism Testing

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-355?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-355: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > HTTP Authentication Mechanism Testing > ------------------------------------- > > Key: ELY-355 > URL: https://issues.jboss.org/browse/ELY-355 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > We don't want to create a full HTTP server but we should have a sufficient wrapper to test the HTTP authentication framework and test out specific mechanims. > This will leave the Elytron Web project to smoke test integration and not focus on testing the actual mechanisms. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-344) Review how clients use ModifiableRealmIdentity / ModifiableRealm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-344?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-344: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Review how clients use ModifiableRealmIdentity / ModifiableRealm > ---------------------------------------------------------------- > > Key: ELY-344 > URL: https://issues.jboss.org/browse/ELY-344 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > This may be something we address in the subsystem but just raising here so we don't forget. > Once we have a working set up with a realm which can be modified it seems unreasonable to expect the administrator to know exactly which credential types and names to use. > This may need to be a few milestones away once we have the bulk integrated so the relationships are clear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-341) PEM file format support

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-341?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-341: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > PEM file format support > ----------------------- > > Key: ELY-341 > URL: https://issues.jboss.org/browse/ELY-341 > Project: WildFly Elytron > Issue Type: Enhancement > Components: KeyStores > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.1.0.Beta8 > > > We should add support for PEM formats for formats including (but not limited to): > * X.509 Certificate > * CSRs > * CRLs > * RSA and DSA Public and Private Keys > * PKCS8 format Private Keys > * DH parameters > * ECDSA Public Key > * EC Private Key > * EC Parameters > This API could be consumed by various utilities or by custom credential storage implementations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-303) Verify compatibility with RFC7617 "The 'Basic' HTTP Authentication Scheme"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-303?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-303: --------------------------------- Fix Version/s: 1.1.0.Beta8 (was: 1.1.0.Beta7) > Verify compatibility with RFC7617 "The 'Basic' HTTP Authentication Scheme" > -------------------------------------------------------------------------- > > Key: ELY-303 > URL: https://issues.jboss.org/browse/ELY-303 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta8 > > > This RFC has now reached the stage of being a proposed standard. > https://www.rfc-editor.org/info/rfc7617 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2016