March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6569) Wrong coded Basic Authentication header gives an OK header back

by Magnus Runesson (JIRA)

Wrong coded Basic Authentication header gives an OK header back --------------------------------------------------------------- Key: JBAS-6569 URL: https://jira.jboss.org/jira/browse/JBAS-6569 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.3.GA Environment: Linux Red Hat Enterprise 5 Reporter: Magnus Runesson Priority: Minor Assume a client post a HTTP-POST-request with an basic authorization header (Authorization: Basic) where the authorizationstring is not properly encoded, i.e. including non BASE-64-characters. The response from JBoss is a 200 OK code and transfer-encoding chunked, ie: HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Transfer-Encoding: chunked It should return a HTTP error 400-code. >From web.xml: <security-constraint> <web-resource-collection> <web-resource-name>alert</web-resource-name> <description>Security config for KEPS.</description> <url-pattern>/path/*</url-pattern> <url-pattern>/path</url-pattern> <http-method>POST</http-method> <http-method>DELETE</http-method> <http-method>PUT</http-method> </web-resource-collection> <auth-constraint> <role-name>foo</role-name> </auth-constraint>  </security-constraint> <security-role> <description>Role for that are allowed to post thunder warnings.</description> <role-name>foo</role-name> </security-role> <login-config> <auth-method>BASIC</auth-method> <realm-name>KEPS</realm-name> </login-config> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1514) Create mechanism to obtain Proxy Factory of Container from @LocalBinding/@RemoteBinding

by Andrew Lee Rubinger (JIRA)

Create mechanism to obtain Proxy Factory of Container from @LocalBinding/@RemoteBinding --------------------------------------------------------------------------------------- Key: EJBTHREE-1514 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1514 Project: EJB 3.0 Issue Type: Task Components: core, proxy Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-Beta4 @see http://fisheye.jboss.org/changelog/JBossAS/?cs=79056 "protected SessionProxyFactory getProxyFactory(RemoteBinding binding)" exists in the Containers, and currently creates a new Proxy Factory each time. We need to be keeping track of each Proxy Factory registered in the JNDI Registrar keyed by its binding so we may retrieve them instead of making all this unnecessary recreation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
6
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-1463) Expose Proxy to ProxyFactory in ProxyObjectFactory

by Andrew Lee Rubinger (JIRA)

[ https://jira.jboss.org/jira/browse/EJBTHREE-1463?page=com.atlassian.jira.... ] Andrew Lee Rubinger resolved EJBTHREE-1463. ------------------------------------------- Resolution: Won't Fix Legacy stuff has now been removed in EJBTHREE-1641, no need for this is present > Expose Proxy to ProxyFactory in ProxyObjectFactory > -------------------------------------------------- > > Key: EJBTHREE-1463 > URL: https://jira.jboss.org/jira/browse/EJBTHREE-1463 > Project: EJB 3.0 > Issue Type: Task > Components: proxy > Reporter: Andrew Lee Rubinger > Assignee: Andrew Lee Rubinger > > Code in StatefulClusterProxyFactory.start() is the legacy example, required for Clustering. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1624) Provide @EJB injection into MC Beans

by Andrew Lee Rubinger (JIRA)

Provide @EJB injection into MC Beans ------------------------------------ Key: EJBTHREE-1624 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1624 Project: EJB 3.0 Issue Type: Feature Request Components: mc-int Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-CR1 Use the EJB Reference Resolver to inject EJBs into MC Beans. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1228) Include org.jboss.ejb3.test.regression.unit Test

by Andrew Lee Rubinger (JIRA)

Include org.jboss.ejb3.test.regression.unit Test ------------------------------------------------ Key: EJBTHREE-1228 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1228 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 This pattern is currently not being run. -- 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

17 years, 3 months

2
14
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1690) jboss-ejb3-core has has a transitive dependency on jboss-servlet-api

by Shelly McGowan (JIRA)

jboss-ejb3-core has has a transitive dependency on jboss-servlet-api -------------------------------------------------------------------- Key: EJBTHREE-1690 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1690 Project: EJB 3.0 Issue Type: Bug Reporter: Shelly McGowan Assignee: Carlo de Wolf Testing Branch_5_0 with the 5.0.1.GA jboss-javee release containing the removal of the jboss-servlet-apis exposed a transitive dependency on those APIs from jboss-ejb3-core: [INFO] +- org.jboss.ejb3:jboss-ejb3-core:jar:client:1.0.0-Beta11:compile [INFO] | +- org.jboss.integration:jboss-jca-spi:jar:5.0.3.GA:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-async:jar:0.1.1:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-cache:jar:0.13.0:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-common:jar:1.0.0-Beta4:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-security:jar:1.0.0-Beta2:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-ext-api:jar:0.4:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-ext-api-impl:jar:0.4.1:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-interceptors:jar:1.0.0-Beta4:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-metadata:jar:0.13.0:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-proxy:jar:1.0.0-Beta6:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-proxy-clustered:jar:1.0.0-Beta3:compile [INFO] | +- org.jboss.ejb3:jboss-ejb3-transactions:jar:1.0.0-Beta1:compile [INFO] | +- org.jboss.javaee:jboss-servlet-api:jar:2.5.0.CR1:compile <============================ [INFO] | +- org.jboss.jpa:jboss-jpa-deployers:jar:1.0.0-Beta4:compile [INFO] | +- sun-jaxws:jaxws-api:jar:2.1.1:compile [INFO] | \- sun-jaxws:jsr181-api:jar:2.1.1:compile My testing is currently being done with an explicit exclusion in component-matrix/pom.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (GPD-280) Release gpd-3.1.7

by Thomas Diesler (JIRA)

Release gpd-3.1.7 ----------------- Key: GPD-280 URL: https://jira.jboss.org/jira/browse/GPD-280 Project: JBoss jBPM GPD Issue Type: Task Reporter: Thomas Diesler Assignee: Koen Aers Fix For: jBPM jPDL Designer 3.1.6 Please release in time for jbpm-3.3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBOOT-17) AbstractServerImpl tries to access /boot.log by default

by Alessio Soldano (JIRA)

AbstractServerImpl tries to access /boot.log by default ------------------------------------------------------- Key: JBBOOT-17 URL: https://jira.jboss.org/jira/browse/JBBOOT-17 Project: JBoss Bootstrap Issue Type: Bug Affects Versions: 1.0.0-Beta-1 Reporter: Alessio Soldano Assignee: Andrew Lee Rubinger By default AbstractServerImpl writes boot.log in the root ("/") which btw fails on *nix if not running from superuser. boot.log used to be written by default in jboss.home/server/jboss.configuration/log along with the server.log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-40) Cannot run embedded tests with SecurityManager

by Thomas Diesler (JIRA)

Cannot run embedded tests with SecurityManager ---------------------------------------------- Key: JBOSGI-40 URL: https://jira.jboss.org/jira/browse/JBOSGI-40 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.x It seem that this is related to the presents of a SecurityManager. Running org.jboss.test.osgi.jbosgi38.OSGI38TestCase java.lang.NoClassDefFoundError: org.osgi.vendor.framework property not set at org.osgi.framework.AdminPermission$ImplHolder.run(AdminPermission.java:166) at java.security.AccessController.doPrivileged(Native Method) at org.osgi.framework.AdminPermission$ImplHolder.<clinit>(AdminPermission.java:153) at org.osgi.framework.AdminPermission.<init>(AdminPermission.java:279) at org.apache.felix.framework.Felix.installBundle(Felix.java:2379) at org.apache.felix.framework.Felix.installBundle(Felix.java:2278) at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:122) at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:108) at org.jboss.test.osgi.jbosgi38.OSGI38TestCase.testInstallStartX(OSGI38TestCase.java:59) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1796) Review project dependencies and create proper abstractions

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1796?page=com.atlassian.jira.plug... ] Jesper Pedersen updated JBAS-1796: ---------------------------------- Attachment: tattletale-report-rev85182.zip > Review project dependencies and create proper abstractions > ---------------------------------------------------------- > > Key: JBAS-1796 > URL: https://jira.jboss.org/jira/browse/JBAS-1796 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Adrian Brock > Priority: Critical > Fix For: Backlog > > Attachments: tattletale-report-rev85182.zip > > > I am getting singlularly fed up with people doing their own integrations > in such a way that every project needs to depend directly on everything > in thirdparty and every other project. > Some people need to go on a course to learn the meaning of abstraction. > e.g. > The server module is an integration project. It should not be directly dependent > on implementation details of Xerces: > package org.jboss.webservice.metadata.wsdl; > import org.apache.xerces.xs.XSComplexTypeDefinition; > import org.apache.xerces.xs.XSTypeDefinition; > import org.jboss.webservice.metadata.wsdl.WSDLConstants; > import org.jboss.webservice.metadata.wsdl.xsd.XSDComplexType; > import org.jboss.webservice.metadata.wsdl.xsd.XSDElement; > import org.jboss.webservice.metadata.wsdl.xsd.XSDSchema; > import org.jboss.webservice.metadata.wsdl.xsd.XSDSimpleType; > import org.jboss.webservice.metadata.wsdl.xsd.XSDType; > import javax.xml.namespace.QName; > import java.io.File; > import java.io.FileWriter; > import java.io.IOException; > import java.lang.reflect.Field; > import java.lang.reflect.Method; > import java.lang.reflect.Modifier; > import java.net.URL; > import java.util.ArrayList; > import java.util.HashMap; > import java.util.Iterator; > import java.util.List; > import java.util.Map; > public class WSDLUtils > { > private String newline = System.getProperty("line.separator"); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 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 2009