April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-138) Check requirements of POST requests

by Darran Lofthouse (JIRA)

Check requirements of POST requests ----------------------------------- Key: SECURITY-138 URL: http://jira.jboss.com/jira/browse/SECURITY-138 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Check the requirements of POST requests when negotiation is used. -- 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

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-206) Attribute type not set in constructor

by Kevin Carlin (JIRA)

Attribute type not set in constructor ------------------------------------- Key: SECURITY-206 URL: http://jira.jboss.com/jira/browse/SECURITY-206 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: 2.0.2.GA Environment: JBoss-5.0.0.Beta4 (Windows XP, Solaris 10, Mac OS X 10.5.2) Reporter: Kevin Carlin Assigned To: Anil Saldhana Priority: Minor Fix For: 2.0.2.GA The constructor public Attribute(URI id, String issuer, DateTimeAttribute issueInstant, AttributeValue value) fails to set the attribute's type. Test case and patch below: JUnit test case. /** * */ package test.attributefinder; import static org.junit.Assert.*; import java.net.URI; import java.net.URISyntaxException; import org.jboss.security.xacml.sunxacml.attr.DateTimeAttribute; import org.jboss.security.xacml.sunxacml.attr.StringAttribute; import org.jboss.security.xacml.sunxacml.ctx.Attribute; import org.junit.Test; /** * @author kevincarlin * */ public class AttributeTest { /** * Test method for {@link org.jboss.security.xacml.sunxacml.ctx.Attribute#Attribute(java.net.URI, java.lang.String, org.jboss.security.xacml.sunxacml.attr.DateTimeAttribute, org.jboss.security.xacml.sunxacml.attr.AttributeValue)}. * @throws Throwable */ @Test public void testAttributeURIStringDateTimeAttributeAttributeValue() throws Throwable { Attribute attribute = new Attribute(new URI("urn:oasis:names:tc:xacml:1.0:resource:resource-id"), "com.enterra.dnipilot", new DateTimeAttribute(), new StringAttribute("Test")); assertNotNull("Attribute type must be set in the constructor", attribute.getType()); } } Patch: Index: security-xacml/trunk/jboss-sunxacml/src/main/java/org/jboss/security/xacml/sunxacml/ctx/Attribute.java =================================================================== --- . (revision 72241) +++ . (working copy) @@ -99,6 +99,7 @@ if(this.attributeValues == null) this.attributeValues = new HashSet<AttributeValue>(); this.attributeValues.add(value); + this.type = value.getType(); } public Attribute(URI id, URI type, String issuer, DateTimeAttribute issueInstant, -- 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

15 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (SECURITY-142) Detect NTLM and log an appropriate error.

by Darran Lofthouse (JIRA)

Detect NTLM and log an appropriate error. ----------------------------------------- Key: SECURITY-142 URL: http://jira.jboss.com/jira/browse/SECURITY-142 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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

15 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (SECURITY-153) Use Base64 from JBoss Common instead of apache-commons-codec

by Darran Lofthouse (JIRA)

Use Base64 from JBoss Common instead of apache-commons-codec ------------------------------------------------------------ Key: SECURITY-153 URL: http://jira.jboss.com/jira/browse/SECURITY-153 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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

15 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (SECURITY-144) Configuration Project

by Darran Lofthouse (JIRA)

Configuration Project --------------------- Key: SECURITY-144 URL: http://jira.jboss.com/jira/browse/SECURITY-144 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse A simple project that allows as much of the configuration as possible to be deployed within a sar. Could this handle the authenticator registration as well? -- 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

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (SECURITY-134) Use of SPNEGOLoginModule results in many authentication failures.

by Darran Lofthouse (JIRA)

Use of SPNEGOLoginModule results in many authentication failures. ----------------------------------------------------------------- Key: SECURITY-134 URL: http://jira.jboss.com/jira/browse/SECURITY-134 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse This may not be an issue but needs to be reviewed. -- 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

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (SECURITY-126) Review username used in SPNEGOAuthenticator

by Darran Lofthouse (JIRA)

Review username used in SPNEGOAuthenticator ------------------------------------------- Key: SECURITY-126 URL: http://jira.jboss.com/jira/browse/SECURITY-126 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse The SPNEGOAuthenticator needs a username in order to be able to call 'authenticate', this username is also used as a unique identifier in the cache. At the moment the session ID for the web application is used. This is unique for the set of current sessions. May cause issues if the ID was to be reused. -- 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

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1302) supported-window-states ignored ? no limitation to normal window only.

by Antoine Herzog (JIRA)

supported-window-states ignored ? no limitation to normal window only. ---------------------------------------------------------------------- Key: JBPORTAL-1302 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1302 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4.1 Final Environment: portal 2.4.1 Reporter: Antoine Herzog Assigned To: Julien Viet In the -object.xml file, remove all window-state elements, but the normal one. <supported-window-states> <window-state>normal</window-state>  </supported-window-states> It does not change anything The min/max icons are still displayed. . And you can still ask for the maximized or minimized state. no exception, the portal still works as usual (with the "classic" all three states enabled). Is it the portal core that should prevent to use these states, if not enabled ? Or the layout strategy and rendering that should not show the icons ? (but then, the portal should warn if we type an url that ask a state that is disabled... even it is not by clicking in the window icon). -- 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

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1052) When running stress tests wrong log4j.xml is picked up

by Tim Fox (JIRA)

When running stress tests wrong log4j.xml is picked up ------------------------------------------------------ Key: JBMESSAGING-1052 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used. This means stress tests are being run on trace logging, which is incorrect (makes them take ages) -- 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

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1126) ClusterViewUpdateTest::testGarbageCollectionOnClusteredCF fails on Hudson

by Tim Fox (JIRA)

ClusterViewUpdateTest::testGarbageCollectionOnClusteredCF fails on Hudson ------------------------------------------------------------------------- Key: JBMESSAGING-1126 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1126 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Clebert Suconic Fix For: AS 5.0 Integration, EAP 4.3 Integration This test fails on Hudson. The test makes assumptions about when Garbage collection is going to occur so IMHO is not a valid test. We cannot ever be sure GC is going to occur - this is up the JVM implementation to decide. The test has been commented out until this is resolved. -- 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

15 years, 9 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008