February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2498) Logout of secured (ssl) admin console setup redirects to http address

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2498?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2498: ----------------------------------------------- FIlip Bogyai <fbogyai(a)redhat.com> changed the Status of [bug 1029687|https://bugzilla.redhat.com/show_bug.cgi?id=1029687] from ON_QA to MODIFIED > Logout of secured (ssl) admin console setup redirects to http address > ---------------------------------------------------------------------- > > Key: WFLY-2498 > URL: https://issues.jboss.org/browse/WFLY-2498 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, Web Console > Reporter: Chris Dolphy > Assignee: Darran Lofthouse > Fix For: 8.0.0.Final > > > Description of problem: > Logging out of an admin console secured with SSL (on port 9443) redirects to http address (e.g. http://localhost:9443/logout?logout) which leads to a Page Not Found error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2696) management audit settings: syslog protocol is lowercase while uppercase is expected

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2696?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2696: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1047519|https://bugzilla.redhat.com/show_bug.cgi?id=1047519] from ON_QA to VERIFIED > management audit settings: syslog protocol is lowercase while uppercase is expected > ----------------------------------------------------------------------------------- > > Key: WFLY-2696 > URL: https://issues.jboss.org/browse/WFLY-2696 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Environment: - 8.0.0 CR1 + latest code in master > - domain mode > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > Fix For: 8.0.0.Final > > > Add a syslog handler to the audit settings of the management service of the domain controller, then start an instance. It fails to start with: > JBAS014612: Operation ("register-server") failed - address: ([]): java.lang.IllegalArgumentException: No enum const class org.jboss.as.controller.audit.SyslogAuditLogHandler$Transport.udp > at java.lang.Enum.valueOf(Enum.java:214) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2912) Generic JMS adapter does not deploy correctly in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2912?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2912: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1064299, https://bugzilla.redhat.com/show_bug.cgi?id=1070106 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1064299) > Generic JMS adapter does not deploy correctly in domain mode. > ------------------------------------------------------------- > > Key: WFLY-2912 > URL: https://issues.jboss.org/browse/WFLY-2912 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Final > Reporter: Tom Ross > Assignee: Stefano Maestri > Fix For: 8.0.1.Final > > > When trying to use generic resource adapter with third part JMS providers like TIBCO it is necessary to use generic RA provided in JBoss EAP 6.2. Unfortunately it would appear that when trying to use in domain mode the RA does not get deployed full, though it works perfectly in standalone mode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3002) ServletContext.getResourcePaths() does'nt meet Spec

by Ercan Oezkan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3002?page=com.atlassian.jira.plugin.... ] Ercan Oezkan commented on WFLY-3002: ------------------------------------ Works! > ServletContext.getResourcePaths() does'nt meet Spec > --------------------------------------------------- > > Key: WFLY-3002 > URL: https://issues.jboss.org/browse/WFLY-3002 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Ercan Oezkan > Assignee: Stuart Douglas > Priority: Critical > Attachments: resource-test.zip > > > Undertow ServletContext.getResourcePaths() does'nt meet the Spec Servlet 2.3. Please see attched Test Web Project resource-test.zip, Undertow does'nt resolve the resources in Child Dependencies located under WEB-INF/lib Folder -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-371) DefaultPropertyReplacer + PropertyResolver is broken for vault expressions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-371?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-371: ------------------------------------------------ Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1058959|https://bugzilla.redhat.com/show_bug.cgi?id=1058959] from POST to MODIFIED > DefaultPropertyReplacer + PropertyResolver is broken for vault expressions > -------------------------------------------------------------------------- > > Key: JBMETA-371 > URL: https://issues.jboss.org/browse/JBMETA-371 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: common > Affects Versions: 7.0.4.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Final > > > The DefaultPropertyReplacer + PropertyResolver algorithm is broken for vault expressions. It's based on the assumption that the contents of the expression string between "${" and "}" have a fixed format a la the old JBoss AS system properties (e.g. propertyname[: default value]) and then the PropertyResolver tries to resolve "propertyname". > This is incorrect in the case of vault expressions, which do not follow this format. In particular the ":" char appears multiple places in a vault expression and does not serve as a delimiter between "propertyname" and "default value". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3026) Security-configuration for messaging wrong in Admin Guide

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3026?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reassigned WFLY-3026: --------------------------------- Assignee: Jeff Mesnil (was: Tom Wells) > Security-configuration for messaging wrong in Admin Guide > --------------------------------------------------------- > > Key: WFLY-3026 > URL: https://issues.jboss.org/browse/WFLY-3026 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.Final > Reporter: Daniel Lechner > Assignee: Jeff Mesnil > Priority: Minor > > In the Admin Guide for Wildfly 8 (https://docs.jboss.org/author/display/WFLY8/Admin+Guide) the section "4.10.2.6 Security Domain for Users" contains an inaccurate snippet. > Following this guide one would suggest that the "security-domain" tag should be an immediate child of subsystem for the messaging. But this raises an exception during startup of the application server. > To configure the security-domain it has to be placed under the "hornetq-server" tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3026) Security-configuration for messaging wrong in Admin Guide

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-3026?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFLY-3026. ------------------------------- Fix Version/s: 8.0.1.Final Resolution: Done update the XML snippets to add enclosing <hornetq-server> elements > Security-configuration for messaging wrong in Admin Guide > --------------------------------------------------------- > > Key: WFLY-3026 > URL: https://issues.jboss.org/browse/WFLY-3026 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.Final > Reporter: Daniel Lechner > Assignee: Jeff Mesnil > Priority: Minor > Fix For: 8.0.1.Final > > > In the Admin Guide for Wildfly 8 (https://docs.jboss.org/author/display/WFLY8/Admin+Guide) the section "4.10.2.6 Security Domain for Users" contains an inaccurate snippet. > Following this guide one would suggest that the "security-domain" tag should be an immediate child of subsystem for the messaging. But this raises an exception during startup of the application server. > To configure the security-domain it has to be placed under the "hornetq-server" tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2753) Workaround for auditlog syslog appName not being configurable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2753?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2753: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1053355|https://bugzilla.redhat.com/show_bug.cgi?id=1053355] from ON_QA to VERIFIED > Workaround for auditlog syslog appName not being configurable > ------------------------------------------------------------- > > Key: WFLY-2753 > URL: https://issues.jboss.org/browse/WFLY-2753 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kyle Lape > Assignee: Kyle Lape > Fix For: 8.0.0.Final > > > Use {{-Dorg.jboss.TEMP.audit.log.appName=customApp}} where the value is the {{app-name}} as mentioned in section 6.2.5 of RFC-5424 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2746) Workaround for auditlog syslog Facility not being configurable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2746?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2746: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> changed the Status of [bug 1052187|https://bugzilla.redhat.com/show_bug.cgi?id=1052187] from ON_QA to VERIFIED > Workaround for auditlog syslog Facility not being configurable > -------------------------------------------------------------- > > Key: WFLY-2746 > URL: https://issues.jboss.org/browse/WFLY-2746 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Final > > > Use -Dorg.jboss.TEMP.audit.log.facility=5 where the number is the FACILITY as mentioned in section 6.2.1 of RFC-5424 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3026) Security-configuration for messaging wrong in Admin Guide

by Daniel Lechner (JIRA)

Daniel Lechner created WFLY-3026: ------------------------------------ Summary: Security-configuration for messaging wrong in Admin Guide Key: WFLY-3026 URL: https://issues.jboss.org/browse/WFLY-3026 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 8.0.0.Final Reporter: Daniel Lechner Assignee: Tom Wells Priority: Minor In the Admin Guide for Wildfly 8 (https://docs.jboss.org/author/display/WFLY8/Admin+Guide) the section "4.10.2.6 Security Domain for Users" contains an inaccurate snippet. Following this guide one would suggest that the "security-domain" tag should be an immediate child of subsystem for the messaging. But this raises an exception during startup of the application server. To configure the security-domain it has to be placed under the "hornetq-server" tag. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 2014