February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8227) Ensure principalVsRolesMap always gets processed when using Elytron regardless of whether or not JACC is enabled

by Farah Juma (JIRA)

Farah Juma created WFLY-8227: -------------------------------- Summary: Ensure principalVsRolesMap always gets processed when using Elytron regardless of whether or not JACC is enabled Key: WFLY-8227 URL: https://issues.jboss.org/browse/WFLY-8227 Project: WildFly Issue Type: Bug Components: Security Reporter: Farah Juma Assignee: Farah Juma We're currently not processing the principalVsRolesMap when using an Elytron security domain with JACC disabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2237) Upgrade Undertow to 1.4.9

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2237?page=com.atlassian.jira.plugi... ] Brian Stansberry closed WFCORE-2237. ------------------------------------ Resolution: Out of Date We're at 1.4.11. > Upgrade Undertow to 1.4.9 > ------------------------- > > Key: WFCORE-2237 > URL: https://issues.jboss.org/browse/WFCORE-2237 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 3.0.0.Alpha22 > Reporter: Paul Ferraro > > Containing fix for https://issues.jboss.org/browse/UNDERTOW-976 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8130) Upgrade WildFly Transaction Client to 1.0.0.Beta14

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8130?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-8130. ------------------------------------ Resolution: Done > Upgrade WildFly Transaction Client to 1.0.0.Beta14 > -------------------------------------------------- > > Key: WFLY-8130 > URL: https://issues.jboss.org/browse/WFLY-8130 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 11.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1063) Improvement: Provide CLI preferences

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1063?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1063: ----------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1139111|https://bugzilla.redhat.com/show_bug.cgi?id=1139111] from NEW to CLOSED > Improvement: Provide CLI preferences > ------------------------------------ > > Key: WFLY-1063 > URL: https://issues.jboss.org/browse/WFLY-1063 > Project: WildFly > Issue Type: Feature Request > Components: CLI > Reporter: Heiko Braun > Assignee: Alexey Loubyansky > Fix For: 8.0.0.Final > > > preferences on for default settings: > [4:37pm] hbraun: CLI preferences would be cool > [4:37pm] hbraun: i am tired of writing recursive=true all the time > alias for address tokens: > [4:38pm] hbraun: plus an address book: prod-db = /subsystem=jadada/database=jadada/ > [4:38pm] hbraun: so you could call prod-db:read-resource -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-456) Add a content-stream attribute to the root deployment=* resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-456?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-456: ------------------------------------ Fix Version/s: 4.0.0.Beta1 > Add a content-stream attribute to the root deployment=* resources > ----------------------------------------------------------------- > > Key: WFCORE-456 > URL: https://issues.jboss.org/browse/WFCORE-456 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 4.0.0.Beta1 > > > Add a new attribute to the deployment resource that allows the user to get a stream with the deployment content attached to the response, a la what we do with the subsystem=logging/log-file=* resource's "stream" attribute. > The attribute must be configured as runtime-only and read-only. > The read handler that handles the attribute should only attach a stream if the following conditions are met, otherwise the value for the attribute should remain as 'undefined'. > 1) The resource's "content" attribute has only a single element in the list. (This is always the case today; adding a check for this is just future proofing) > 2) The first element in the "content" attribute list has a defined value in its "hash" field. (This confirms the content is stored in the content repo. We won't support serving unmanaged content as we have insufficient control over it.) > 3) The first element in the "content" attribute list has a 'true' as value of its "archive" field. (Current this will always be the case; this is future proofing for when we add support for exploded content in the content repo. Trying to assemble a stream from exploded content is currently out of scope for this feature.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8226) Update default domain configuration to use remote+http

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-8226: -------------------------------------- Summary: Update default domain configuration to use remote+http Key: WFLY-8226 URL: https://issues.jboss.org/browse/WFLY-8226 Project: WildFly Issue Type: Enhancement Components: Domain Management Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Fix For: 11.0.0.Alpha1 Our default domain configuration still use the native remote protocol on port 9999 for DC-HC communication. Update those files so that we use http-remoting on port 9990. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6409) Update default domain configuration to use remote+http

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6409?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6409: ----------------------------------- Priority: Major (was: Minor) > Update default domain configuration to use remote+http > ------------------------------------------------------ > > Key: WFLY-6409 > URL: https://issues.jboss.org/browse/WFLY-6409 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 11.0.0.Alpha1 > > > Our default domain configuration still use the native remote protocol on port 9999 for DC-HC communication. Update those files so that we use http-remoting on port 9990. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6565) add and remove operation of jaxrs subsystem under deployment are useles and should not be available

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6565?page=com.atlassian.jira.plugin.... ] Brian Stansberry reopened WFLY-6565: ------------------------------------ Reopening to align with the downstream issue, which QE reopened. Let's just drop these handlers. If there's any logic that is counting on executing them it is almost certainly broken. > add and remove operation of jaxrs subsystem under deployment are useles and should not be available > --------------------------------------------------------------------------------------------------- > > Key: WFLY-6565 > URL: https://issues.jboss.org/browse/WFLY-6565 > Project: WildFly > Issue Type: Bug > Components: REST > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 11.0.0.Alpha1 > > > *Description of problem:* > "add" and "remove" operation of jaxrs subsystem under deployment are useles and should not be available. > This operations were added by WFLY-3045. > *How reproducible:* > Always > *Steps to Reproduce (remove):* > # ./standalone.sh > # deploy /home/mkopecky/playground/resteasy/single-application/target/jaxrs-eap.war > # /deployment=jaxrs-eap.war/subsystem=jaxrs:remove > # :reload > # # jaxrs subsystem is not removed > *Steps to Reproduce (add):* > # deploy /home/mkopecky/playground/resteasy/empty-deployment/target/empty-eap.war > # /deployment=empty-eap.war/subsystem=jaxrs:add() > # :reload > # # jaxrs subsystem is not added -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-449) Add CredentialStore support to Elytron client configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-449?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-449: --------------------------------- Fix Version/s: 1.1.0.Beta28 (was: 1.1.0.Beta27) > Add CredentialStore support to Elytron client configuration > ----------------------------------------------------------- > > Key: ELY-449 > URL: https://issues.jboss.org/browse/ELY-449 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Authentication Client, Credential Store > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta28 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-455) OAuth2 Credential Store

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-455?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-455: --------------------------------- Fix Version/s: 1.1.0.Beta28 (was: 1.1.0.Beta27) > OAuth2 Credential Store > ----------------------- > > Key: ELY-455 > URL: https://issues.jboss.org/browse/ELY-455 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Credential Store > Reporter: David Lloyd > Assignee: Pedro Igor > Fix For: 1.1.0.Beta28 > > > Need an OAuth2 credential store which can acquire a cached OAuth2 token or instigate a new authentication. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017