November 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1382) VERIFY_SUSPECT can kick a live node soon after it re-joins

by Dennis Reed (Created) (JIRA)

VERIFY_SUSPECT can kick a live node soon after it re-joins ---------------------------------------------------------- Key: JGRP-1382 URL: https://issues.jboss.org/browse/JGRP-1382 Project: JGroups Issue Type: Bug Affects Versions: 2.6.20 Reporter: Dennis Reed Assignee: Dennis Reed Due to a timing issue, VERIFY_SUSPECT can kick a good member from the cluster soon after joining. A live node currently in the cluster stops responding temporarily (garbage collection, NIC down, etc). FD sends up a suspect message to VERIFY_SUSPECT. VERIFY_SUSPECT times out and sends up the suspect message. Before the node is kicked from the cluster, FD sends up another suspect message to VERIFY_SUSPECT. Node is kicked from the cluster. Node resumes, is shunned, and rejoins. VERIFY_SUSPECT times out and sends up the suspect message. Node is kicked from the cluster again. -- 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

14 years, 8 months

5
7
0 / 0

[JBoss JIRA] (SECURITY-630) Backwards compatibility with JBoss 5

by Marek Posolda (Created) (JIRA)

Backwards compatibility with JBoss 5 ------------------------------------ Key: SECURITY-630 URL: https://issues.jboss.org/browse/SECURITY-630 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.1.0 Reporter: Marek Posolda Assignee: Darran Lofthouse Fix For: Negotiation_2.1.1 There are some new features in JBoss Negotiation 2.1.0 (especially fallback to form aka SECURITY-141 ), which will be nice to have in EPP 5.2. EPP 5 is based on JBoss 5 (JBoss web 2.x) and unfortunately JBoss Negotiation has been upgraded to be API compatible with JBoss 6 (JBoss web 3). Main problem problem especially signature of method NegotiationAuthenticator.authenticate(final Request request, final HttpServletResponse response, final LoginConfig config) where in JBoss 5 signature of method was authenticate(final Request request, final Response response, final LoginConfig config) This means that using NegotiationAuthenticator from Negotiation 2.1.0 is not working in JBoss 5 due to this compatibility problem. Unfortunately approaches like inheritance of NegotiationAuthenticator are not working because there is also change in signature of method AuthenticatorBase.register . It will be nice to have backwards compatibility with JBoss 5, which is possible by adding methods with old signature into class NegotiationAuthenticator, and with this approach it should work in both JBoss 5 and JBoss 6. -- 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

14 years, 8 months

6
6
0 / 0

[JBoss JIRA] (AS7-2132) Remove JNP sockets from server configuration

by David Lloyd (Created) (JIRA)

Remove JNP sockets from server configuration -------------------------------------------- Key: AS7-2132 URL: https://issues.jboss.org/browse/AS7-2132 Project: Application Server 7 Issue Type: Task Components: JMS Reporter: David Lloyd Assignee: Clebert Suconic Priority: Critical Fix For: 7.1.0.Beta1 The JNP socket configuration introduced for HQ should be eliminated. -- 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

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] (SECURITY-631) Possibility to choose principal identity from FORM authentication

by Marek Posolda (Created) (JIRA)

Possibility to choose principal identity from FORM authentication ----------------------------------------------------------------- Key: SECURITY-631 URL: https://issues.jboss.org/browse/SECURITY-631 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.1.0 Reporter: Marek Posolda Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP4 , Negotiation_2.1.1 Currently method SPNEGOLoginModule.usernamePasswordLogin() is performing FORM-based authentication and when authenticates, it choose first principal from obtained subject and call setIdentity() with this principal. In EPP login modules, our subject has more principals and user principal is not returned as first principal of subject. For handle this situation, it will be nice to have this functionality in protected method like: {code} protected Principal getIdentityFromSubject(Subject userSubject) { Set principals = userSubject.getPrincipals(); if (principals.isEmpty()) { throw new LoginException("No principal returned after login."); } else if (principals.size() > 1) { log.warn("Multiple principals returned, using first principal in set."); } Principal identity = (Principal) principals.iterator().next(); return identity; } {code} which will be called from usernamePasswordLogin(). So that it will be possible to create subclass of SPNEGOLoginModule and override functionality of always choosing first principal. -- 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

14 years, 8 months

5
4
0 / 0

[JBoss JIRA] Created: (SECURITY-132) Traditional Authentication

by Darran Lofthouse (JIRA)

Traditional Authentication -------------------------- Key: SECURITY-132 URL: http://jira.jboss.com/jira/browse/SECURITY-132 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Incomming call may be traditional username / password type call but consideration needs to be given for potential outbound call. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (SECURITY-141) Fallback to different authenticator if authentication fails

by Darran Lofthouse (JIRA)

Fallback to different authenticator if authentication fails ----------------------------------------------------------- Key: SECURITY-141 URL: http://jira.jboss.com/jira/browse/SECURITY-141 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Need to consider how this will work especially regarding security domains, possible to do something active directory - password-stacking and an LDAP login module that for negotiation does just role mapping and for non negotiation also does authentication. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (SECURITY-565) Fix hardcoded server name for SPNEGOSockets

by Marcus Moyses (JIRA)

Fix hardcoded server name for SPNEGOSockets ------------------------------------------- Key: SECURITY-565 URL: https://issues.jboss.org/browse/SECURITY-565 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP3 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: Negotiation_2.0.3.SP4 A hardcoded server name was incorrectly set in the client side starting a negotiation handshake. Now the server name can be set on the client side using the org.jboss.security.negotiation.server.principal system property. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[JBoss JIRA] (AS7-2307) Provide JAXR HTTP endpoint

by Thomas Diesler (Created) (JIRA)

Provide JAXR HTTP endpoint -------------------------- Key: AS7-2307 URL: https://issues.jboss.org/browse/AS7-2307 Project: Application Server 7 Issue Type: Task Components: JAXR Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.CR1 -- 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

14 years, 8 months

4
3
0 / 0

[JBoss JIRA] (AS7-2395) Restore JAXR test coverage

by Thomas Diesler (Created) (JIRA)

Restore JAXR test coverage -------------------------- Key: AS7-2395 URL: https://issues.jboss.org/browse/AS7-2395 Project: Application Server 7 Issue Type: Task Components: JAXR, Test Suite Reporter: Thomas Diesler Fix For: 7.1.0.CR1 $ mvn -Dtest=jaxr/**/*TestCase test {code} Running org.jboss.as.test.integration.jaxr.scout.basic.JaxrJNDIConnectionTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.007 sec Running org.jboss.as.test.integration.jaxr.scout.query.infomodel.JaxrFindAssociationsTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.013 sec <<< FAILURE! Running org.jboss.as.test.integration.jaxr.scout.query.JaxrBusinessQueryTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.001 sec <<< FAILURE! Running org.jboss.as.test.integration.jaxr.scout.publish.JaxrDeleteOrganizationTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.001 sec <<< FAILURE! Running org.jboss.as.test.integration.jaxr.scout.publish.JaxrDeleteAssociationTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.004 sec <<< FAILURE! Running org.jboss.as.test.integration.jaxr.scout.publish.infomodel.JaxrConfimAssociationTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.001 sec <<< FAILURE! Running org.jboss.as.test.integration.jaxr.scout.publish.infomodel.JaxrClassficationTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0 sec <<< FAILURE! Running org.jboss.as.test.integration.jaxr.scout.publish.JaxrSaveOrganizationTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0 sec <<< FAILURE! Running org.jboss.as.test.integration.jaxr.scout.publish.JaxrSaveServiceBindingTestCase Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.001 sec <<< FAILURE! {code} -- 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

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-2499) Remove DirContext hack to load juddi.properties

by Thomas Diesler (Created) (JIRA)

Remove DirContext hack to load juddi.properties ----------------------------------------------- Key: AS7-2499 URL: https://issues.jboss.org/browse/AS7-2499 Project: Application Server 7 Issue Type: Task Components: JAXR, Web Reporter: Thomas Diesler Assignee: Kurt Stam JBossWeb Context API does not allow to register resources adequately. -- 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

14 years, 8 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 November 2011