November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1543) RELAY2: provide SITE-UNREACHABLE notifications

by Bela Ban (JIRA)

Bela Ban created JGRP-1543: ------------------------------ Summary: RELAY2: provide SITE-UNREACHABLE notifications Key: JGRP-1543 URL: https://issues.jboss.org/browse/JGRP-1543 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.3 Provide notifications when a site is down, every time a message is sent to a SiterMaster(X) and X is down, a notification SITE-UNREACHABLE should be emitted. This can be: - A SITE_UNREACHABLE event being sent up the stack of the message sender - A callback being invoked on registered listeners in RELAY2 -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] (AS7-5742) Provide a feature switch (compile & runtime time)

by Heiko Braun (JIRA)

Heiko Braun created AS7-5742: -------------------------------- Summary: Provide a feature switch (compile & runtime time) Key: AS7-5742 URL: https://issues.jboss.org/browse/AS7-5742 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] (JBJCA-917) @ConfigProperty annotation does not hand the superclass's value over to the subclass

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created JBJCA-917: ----------------------------------------- Summary: @ConfigProperty annotation does not hand the superclass's value over to the subclass Key: JBJCA-917 URL: https://issues.jboss.org/browse/JBJCA-917 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.1.0.Beta2, 1.0.13.Final Reporter: Vladimir Rastseluev Assignee: Jesper Pedersen Fix For: 1.0.14.Final, 1.1.0.Beta3 See @Ignored test in case: org.jboss.jca.test.deployers.spec.rars.testcases.Ra16inoutijmultiannoTestCase -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] (JBJCA-915) Activation of connector 1.5 archive doesn't happen, when ironjacamar.xml doesn't contain class-names

by Vladimir Rastseluev (JIRA)

Vladimir Rastseluev created JBJCA-915: ----------------------------------------- Summary: Activation of connector 1.5 archive doesn't happen, when ironjacamar.xml doesn't contain class-names Key: JBJCA-915 URL: https://issues.jboss.org/browse/JBJCA-915 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.1.0.Beta2, 1.0.13.Final Reporter: Vladimir Rastseluev Assignee: Jesper Pedersen Fix For: 1.0.14.Final, 1.1.0.Beta3 In corner case, when deployed .rar, containing 1 connection definition and 1 admin object and ironjacamar.xml file contains <connection-definition> and <admin-object> elements both without "class-name" attribute, activation doesn't happen. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] (JBJCA-841) Deployers test suite

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-841: ------------------------------------- Summary: Deployers test suite Key: JBJCA-841 URL: https://issues.jboss.org/browse/JBJCA-841 Project: IronJacamar Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Vladimir Rastseluev Fix For: 1.1.0.Beta2 * Clean up deployers/ test suite for duplicated tests * Improve code coverage, especially for resource adapter v1.0 * Remove incorrect DTD tests for v1.5 and v1.6 * Give descriptive names for test classes and resources -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBJCA-925) Expand annotation test suite

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-925: ------------------------------------- Summary: Expand annotation test suite Key: JBJCA-925 URL: https://issues.jboss.org/browse/JBJCA-925 Project: IronJacamar Issue Type: Task Components: Common Reporter: Jesper Pedersen Assignee: Vladimir Rastseluev Fix For: 1.0.14.Final, 1.1.0.Beta3 Expand the annotation test suite, especially with applying empty / partial definitions up front, then full indexes afterwards -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] (JBJCA-895) Advanced security inflow

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-895: ------------------------------------- Summary: Advanced security inflow Key: JBJCA-895 URL: https://issues.jboss.org/browse/JBJCA-895 Project: IronJacamar Issue Type: Task Components: Common, Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta3 Allow security inflow based on 16.4.3 and 16.4.4 to be defined per deployment instead of container wide -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4391) admin console proxying vs header Origin

by Aleksandar Kostadinov (JIRA)

Aleksandar Kostadinov created AS7-4391: ------------------------------------------ Summary: admin console proxying vs header Origin Key: AS7-4391 URL: https://issues.jboss.org/browse/AS7-4391 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Reporter: Aleksandar Kostadinov Assignee: Heiko Braun When using a reverse proxy to access AS7 console and a browser that sets the header Origin, 403 is returned due to mismatch between Origin and Host headers. Run the server on localhost for example by: bin/domain.sh Run apache httpd with the following configuration (e.g. in /etc/httpd/conf.d/proxy_console.conf): ProxyPassReverseCookieDomain localhost <your server public hostname> ProxyPassReverse / http://localhost:9990/ ProxyPass / http://localhost:9990/ These should work: open http://<your server public hostname> with firefox or IE - this should work curl -v -u "adminusername:adminpassword" --digest http://localhost:9990/management/ # on the server this should work These fail: open http://<your server public hostname> with chromium curl -v -u "adminusername:adminpassword" -H "Origin: http://<your server public hostname>" --digest http://localhost:9990/management/ What happens is that Chromium correctly sets the Origin header to the server public IP hostname. mod_proxy keeps that header but sets Host to localhost:9990. Console sees the mismatch and returns 403. Firefox and IE do not set that header so they work. That protection of admin console was introduced in: https://issues.jboss.org/browse/AS7-2400 https://github.com/jbossas/jboss-as/commit/29cf3610d8dab1af0227842d877b92... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
8
0 / 0

[JBoss JIRA] (AS7-2812) Add message in CLI to indicate which authentication method was used.

by Darran Lofthouse (Created) (JIRA)

Add message in CLI to indicate which authentication method was used. -------------------------------------------------------------------- Key: AS7-2812 URL: https://issues.jboss.org/browse/AS7-2812 Project: Application Server 7 Issue Type: Task Components: CLI, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.CR1 I need to review if this is feasible but there are a number of reports coming in where end users believe their server is not secured because our local / silent mechanism is working so quietly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
8
0 / 0

[JBoss JIRA] (AS7-3112) Better integration of service based ServerAuthenticationProviders

by Darran Lofthouse (Created) (JIRA)

Better integration of service based ServerAuthenticationProviders ----------------------------------------------------------------- Key: AS7-3112 URL: https://issues.jboss.org/browse/AS7-3112 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final The security configuration of Remoting within AS7 is based on supplying three things: - - The ServerAuthenticationProvider to obtain mechanism specific CallbackHanlders - The OptionMap to control the security mechanisms made available / mandated. - Possibly an initialised SSLContext for XnioSsl if SSL is being enabled. For domain management the capabilities of the backing realm are used to define the security offered i.e. if we have no SSL configuration we can not enable SSL, if the backing store can not return the plain text passwords we can not enable DIGEST. This has been achieved so far by using an intermediary service to define the configuration based on capabilities alone. This task it to take it one step further and allow this intermediary to be defined within the Remoting subsystem and maybe an equivalent for pure domain management to act as both a intermediary to define configuration based on the realm and also to allow additional configuration overrides. i.e. we need to support the additional SASL options available and SSL options available - this will somehow need to be merged / validated with the realm capabilities e.g. if a Realm is incompatible with Digest a user can not force the use of Digest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012