April 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6490) Undertow listener's 'enabled' attribute should not require reload to go from false to true

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-6490: -------------------------------------- Summary: Undertow listener's 'enabled' attribute should not require reload to go from false to true Key: WFLY-6490 URL: https://issues.jboss.org/browse/WFLY-6490 Project: WildFly Issue Type: Enhancement Components: Web (Undertow) Reporter: Brian Stansberry Assignee: Brian Stansberry In general an 'enabled' type attribute shouldn't require a reload to go from 'false' to 'true'. Turning something on generally isn't disruptive to other currently running services. It's turning things off that can be problematic. While not a focus of this JIRA, possibly even the true -> false case could be supported via the "allow-resource-service-restart" => true header, although that needs a bit more thought. Over the years I've gone back and forth on the wisdom of making support for that more widespread. It adds flexibility at the risk of making it easier for users to screw up. These days though I'm trending back toward thinking it's a good thing to support. Side note: 'enabled' attributes are better avoided in the first place. :) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-272) When loading a RealmIdentity with no attributes, make sure we get an empty modifiable AttributesImpl

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-272?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-272: --------------------------------- Fix Version/s: 1.1.0.Beta6 (was: 1.1.0.Beta5) > When loading a RealmIdentity with no attributes, make sure we get an empty modifiable AttributesImpl > ---------------------------------------------------------------------------------------------------- > > Key: ELY-272 > URL: https://issues.jboss.org/browse/ELY-272 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.1.0.Beta6 > > > Currently only FileSystemRealm is modifiable -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-263) Revisit ServerAuthenticationContext.querySaslServerMechanismNames

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-263?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-263: --------------------------------- Fix Version/s: 1.1.0.Beta6 (was: 1.1.0.Beta5) > Revisit ServerAuthenticationContext.querySaslServerMechanismNames > ----------------------------------------------------------------- > > Key: ELY-263 > URL: https://issues.jboss.org/browse/ELY-263 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta6 > > > Does this method still have a use? > If so we probably need to adjust all filtering factory implements to support the query all flag. > Also if it does HTTP may need the same treatment. > If not maybe we remove the whole method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[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.Beta6 (was: 1.1.0.Beta5) > 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.Beta6 > > > 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)

10 years, 1 month

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.1.0.Beta6 (was: 1.1.0.Beta5) > 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.1.0.Beta6 > > > 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.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-200) Add a set of standard HTTP authentication mechanisms

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-200?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-200: --------------------------------- Fix Version/s: 1.1.0.Beta6 (was: 1.1.0.Beta5) > Add a set of standard HTTP authentication mechanisms > ---------------------------------------------------- > > Key: ELY-200 > URL: https://issues.jboss.org/browse/ELY-200 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta6 > > > i.e. BASIC, DIGEST, CLENT_CERT, FORM (Generic), SPNEGO -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-19) OAuth Broker Security Realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-19?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-19: -------------------------------- Fix Version/s: 1.1.0.Beta6 (was: 1.1.0.Beta5) > OAuth Broker Security Realm > --------------------------- > > Key: ELY-19 > URL: https://issues.jboss.org/browse/ELY-19 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Pedro Igor > Fix For: 1.1.0.Beta6 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-353) Add NameRewriters to map from mechanism credential name to the name presented to the realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-353?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-353: --------------------------------- Fix Version/s: 1.1.0.Beta6 (was: 1.1.0.Beta5) > Add NameRewriters to map from mechanism credential name to the name presented to the realm > ------------------------------------------------------------------------------------------ > > Key: ELY-353 > URL: https://issues.jboss.org/browse/ELY-353 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta6 > > > Names may not be consistent across realm implementations so a level of mapping may be required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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.Beta6 (was: 1.1.0.Beta5) > 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 > Fix For: 1.1.0.Beta6 > > > 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)

10 years, 1 month

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.Beta6 (was: 1.1.0.Beta5) > 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.Beta6 > > > 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)

10 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 April 2016