March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4680) Logout a remote client from server and clearing login module cache.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4680?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4680: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Logout a remote client from server and clearing login module cache. > ------------------------------------------------------------------- > > Key: AS7-4680 > URL: https://issues.jboss.org/browse/AS7-4680 > Project: Application Server 7 > Issue Type: Feature Request > Components: Remoting, Security, Server > Affects Versions: 7.1.1.Final > Environment: java 1.6 > win 7 64 bit > 4 gb ram > Reporter: Serkan Yıldırım > Assignee: Darran Lofthouse > Labels: Remoting_Management, jboss-as7, login-module, logout, remoting, security > Fix For: 8.0.0.Alpha1 > > > I have a custom login module. I authenticate and authorize a user (creating roles) by using this custom module. When i close the remote application, i want to logout the user from server so that clear login module cache, i.e deleting principals and roles from the cache. I couldn't find a solution for this problem in forum. If it exists, could you please explain it, thanks. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4648) mod_proxy incompatible with logout mechanism

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4648?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4648: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > mod_proxy incompatible with logout mechanism > -------------------------------------------- > > Key: AS7-4648 > URL: https://issues.jboss.org/browse/AS7-4648 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Domain Management > Reporter: Jason Greene > Assignee: Jason Greene > Fix For: 8.0.0.Alpha1 > > Attachments: apache_mod_proxy_mgmt.conf, Screenshot_proxy_logs.png > > > We need to either outlaw proxies, or to make sure the console works with them. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6038) Remove DeploymentScanner's bootTimeScan method

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6038?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6038: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Remove DeploymentScanner's bootTimeScan method > ---------------------------------------------- > > Key: AS7-6038 > URL: https://issues.jboss.org/browse/AS7-6038 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Chao Wang > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The DeploymentScanner interface's bootTimeScan method isn't implemented and isn't used and should be removed. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4626) Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4626?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4626: ---------------------------------- Fix Version/s: (was: 7.3.0.Alpha1) > Standard method of documenting whether expressions are supported in the jboss-as-config_x_x.xsd and in the subsystem xsds > ------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-4626 > URL: https://issues.jboss.org/browse/AS7-4626 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > > Users should be able to read the xsd to tell if expressions are supported for a given attribute/element. Reading the management API metadata is too cumbersome and indirect. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5583) Allow defining server http port (and other basic properties) via jvm arguments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5583?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5583: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Allow defining server http port (and other basic properties) via jvm arguments > ------------------------------------------------------------------------------ > > Key: AS7-5583 > URL: https://issues.jboss.org/browse/AS7-5583 > Project: Application Server 7 > Issue Type: Feature Request > Components: Build System, Domain Management > Affects Versions: 7.1.1.Final > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 8.0.0.Alpha1 > > > Currently the only way to specify server port is to edit server configuration .xml. However there are cases which could use definition via jvm arg. Forums shows the following workaround (https://community.jboss.org/thread/168140). I'd like to propose to include in default jboss-as standalone.xml configuration, properties for the most important parameters: > eg. > change <socket-binding name="http" port="8080"/> to > <socket-binding name="http" port="${jboss.http.port:8080}"/> > Then would be possible to run jboss on different port via jvm arg > ./bin/standalone.sh --server-config=standalone-ha.xml -Djboss.http.port=8888 > Solving this issue is important, because some other issues relies on it: eg. https://issues.jboss.org/browse/AS7-1036 > With this change, solving mentioned ticket would be very easy, and will allow to run arquillian tests directly on jboss downloaded and unpacked via maven goal, and then managed directly via arquillian (it is the only way to run arquillian tests in some environments, however often 8080 port is already used). > I'm willing to solve this feature by myself, however I'd like to hear opinions from other people. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5950) Streamline :read-resource-description

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5950?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5950: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Streamline :read-resource-description > ------------------------------------- > > Key: AS7-5950 > URL: https://issues.jboss.org/browse/AS7-5950 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > We have a need for a streamlined read-resource-description operation response. In many cases we only need the attribute descriptions and from those descriptions only a subset of the meta data available. > For instance: > {noformat} > "enable-statistics" => { > "type" => BOOLEAN, > "description" => "Whether statistics should be enabled.", > "expressions-allowed" => true, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {noformat} > Clients that require information about the structure don't need: > - access-type > - storage > - restart-required > In many cases we don't even need > - operations > - children > Would it be possible to further parametrize the read-resource-description operation to allow these distinctions? This would help to reduce the overall payload size when clients communicate with the DC and improve thus improve the overall performance. Not to mention parsing greatly benefits from a streamlined model as well. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5418) Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5418?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5418: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Resource description for platform mbean properties that throw UnsupportedOperationException should say nillable="true" > ---------------------------------------------------------------------------------------------------------------------- > > Key: AS7-5418 > URL: https://issues.jboss.org/browse/AS7-5418 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Environment: FreeBSD, OpenJDK 1.6 > Reporter: Brian Stansberry > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Some platform mbean getters are documented to throw a UOE on some VMs. The read-resource handler will catch the UOE and leave the attribute undefined, but the description says it's not nillable. > Specifically, PlatformMBeanDescriptions.getThreadingResource()'s THREAD_CPU_TIME_ENABLED attribute, although there may well be others. > This leads to this unit test failure on jvms where the UOE is thrown: > failure message="thread-cpu-time-enabled is undefined" > type="junit.framework.AssertionFailedError">junit.fra mework.AssertionFailedError: thread-cpu-time-enabled is undefined > at junit.framework.Assert.fail(Assert.java:50) > at junit.framework.Assert.assertTrue(Assert.java:20) > at > org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.validateResource(PlatformMBeanResourceUn > itTestCase.java:595) > at org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.basicResourceTest(PlatformMBeanResourceUnitTestCase.java:563) > at > org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.testThreadingMXBean(PlatformMBeanResourceUnitTestCase.java:340) -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5503) Move DC operation stream cleaning from OperationCoordinatorStepHandler and into the OSHs that actual process the input streams

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5503?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5503: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Move DC operation stream cleaning from OperationCoordinatorStepHandler and into the OSHs that actual process the input streams > ------------------------------------------------------------------------------------------------------------------------------ > > Key: AS7-5503 > URL: https://issues.jboss.org/browse/AS7-5503 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Get rid of hackaliciousness at [1] and replace using OperationAttachments the way Stuart did for deployment overlays. > [1] https://github.com/jbossas/jboss-as/blob/master/host-controller/src/main/... -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5522) Convert deployment's content to a child resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5522?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5522: ---------------------------------- Fix Version/s: (was: 7.3.0.Alpha1) > Convert deployment's content to a child resource > ------------------------------------------------ > > Key: AS7-5522 > URL: https://issues.jboss.org/browse/AS7-5522 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > > At the moment this is a complex attribute. > Not saying this MUST happen, just opening this to see what Brian & co think. I never really understood why it is a list either. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5338) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5338?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5338: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users > --------------------------------------------------------------------------------------------- > > Key: AS7-5338 > URL: https://issues.jboss.org/browse/AS7-5338 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) > But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- 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

13 years, 4 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 March 2013