January 2016 - jboss-jira - Jboss List Archives

[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.Beta5 > 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.Beta5 > > > 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)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6076) CLI deployment of WAR exploded JSF2.2 applications fails with exceptions

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-6076?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-6076: ---------------------------------- Do you have a simple reproducer app you can share? > CLI deployment of WAR exploded JSF2.2 applications fails with exceptions > ------------------------------------------------------------------------ > > Key: WFLY-6076 > URL: https://issues.jboss.org/browse/WFLY-6076 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.0.0.CR5 > Reporter: Miroslav Pavleski > Assignee: Farah Juma > Attachments: cli.log, console.log > > > In 9.0.2 FINAL and prior (8.1, 8.2) deploying an exploded WAR using the CLI was working fine. This kind of deployment has benefits during development as the static resources are updated on-save. > The problem occurs probably due JSF initialization, see the attachments. > Deployment using mvn wildfly:deploy works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-107: -------------------------------------- Probably also worth considering the reference to the security domain could be optional - this way we get the same capability to return the SSLContext instances but where no trust decisions are being made we don't need it backed by a security domain. > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-107: -------------------------------------- I think this is actually likely to sit in a similar position to the HTTP and SASL 'AuthenticationFactory' objects - i.e. some form of policy object that will reference a security domain but will also reference other relevant capabilities to fully assemble the SSLContext. Being a policy object it will also be able to hold things such as protocol and cipher suite rules. > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6081) Undertow migration operation doesn't migrate Access log valves

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-6081?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet updated WFLY-6081: ------------------------------------ Summary: Undertow migration operation doesn't migrate Access log valves (was: [Migration][WebToUndertow] Access log valves are not automaticaly migrated) > Undertow migration operation doesn't migrate Access log valves > -------------------------------------------------------------- > > Key: WFLY-6081 > URL: https://issues.jboss.org/browse/WFLY-6081 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Access log valves are not automatically migrated, it should be either printed warning for them to be migrated automatically or migrated automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-107: --------------------------------- Labels: elytron_ssl (was: ) > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-107: --------------------------------- Fix Version/s: 1.1.0.Beta4 (was: 1.1.0.CR1) > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6081) [Migration][WebToUndertow] Access log valves are not automaticaly migrated

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-6081?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet reassigned WFLY-6081: --------------------------------------- Assignee: ehsavoie Hugonnet (was: Stuart Douglas) > [Migration][WebToUndertow] Access log valves are not automaticaly migrated > -------------------------------------------------------------------------- > > Key: WFLY-6081 > URL: https://issues.jboss.org/browse/WFLY-6081 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Access log valves are not automatically migrated, it should be either printed warning for them to be migrated automatically or migrated automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6081) [Migration][WebToUndertow] Access log valves are not automaticaly migrated

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-6081?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet moved JBEAP-3074 to WFLY-6081: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6081 (was: JBEAP-3074) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) (was: Migration) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR5 (was: 7.0.0.ER4) > [Migration][WebToUndertow] Access log valves are not automaticaly migrated > -------------------------------------------------------------------------- > > Key: WFLY-6081 > URL: https://issues.jboss.org/browse/WFLY-6081 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Reporter: ehsavoie Hugonnet > Assignee: Stuart Douglas > > Access log valves are not automatically migrated, it should be either printed warning for them to be migrated automatically or migrated automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5939) Binding to <any-address/> will make mod_cluster advertise host as 0.0.0.0

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5939?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-5939. -------------------------------- > Binding to <any-address/> will make mod_cluster advertise host as 0.0.0.0 > ------------------------------------------------------------------------- > > Key: WFLY-5939 > URL: https://issues.jboss.org/browse/WFLY-5939 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR5 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.Final > > > Needs to be handled in {{org.wildfly.mod_cluster.undertow.UndertowConnector#setAddress}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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