February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3781) Stateful SB Instance Interceptor should not push SubjectContext if RunAsIdentity present

by Anil Saldhana (JIRA)

Stateful SB Instance Interceptor should not push SubjectContext if RunAsIdentity present ---------------------------------------------------------------------------------------- Key: JBAS-3781 URL: http://jira.jboss.com/jira/browse/JBAS-3781 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1, JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2, JBossAS-4.0.6.CR1 The following Subject Context push (with null Subject) to establish client security context should not be performed if the user has configured a RunAsIdentity in the caller bean. /* The security context must be established before the cache lookup because the activation of a session should have the caller's security context as ejbActivate is allowed to call other secured resources. Since the pm makes the ejbActivate call, we need to set the caller's security context. The only reason this shows up for stateful session is that we moved the SecurityInterceptor to after the instance interceptor to allow security exceptions to result in invalidation of the session. This may be too literal an interpretation of the ejb spec requirement that runtime exceptions should invalidate the session. */ SecurityActions.pushSubjectContext(mi.getPrincipal(), mi.getCredential(), null); The resolution is: if(SecurityActions.peekRunAsIdentity() == null) SecurityActions.pushSubjectContext(mi.getPrincipal(), mi.getCredential(), null); -- 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

19 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-104) DeploymentContext shortName for jar is messed up as well as url

by Bill Burke (JIRA)

DeploymentContext shortName for jar is messed up as well as url --------------------------------------------------------------- Key: JBMICROCONT-104 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-104 Project: JBoss MicroContainer Issue Type: Bug Components: Container Reporter: Bill Burke The DeploymentContext.getName() ends up being the full URL of a JAR if you have a JAR file within a directory, its name is jar:file:/.../foo.jar!/ Shouldn't this be a "short" name? My bet this has something to do with how the URL is messed up too for VirtualFiles that are JARs. -- 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

19 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBREM-634) update doc on callbacks

by Tom Elrod (JIRA)

update doc on callbacks ----------------------- Key: JBREM-634 URL: http://jira.jboss.com/jira/browse/JBREM-634 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.2.0.Alpha3 (Bluto) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Update doc to include more info on callbacks, especially changes made for JBREM-622 -- 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

19 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-335) Create a Maven plugin version of JBossRetro

by Paul Gier (JIRA)

Create a Maven plugin version of JBossRetro ------------------------------------------- Key: JBBUILD-335 URL: http://jira.jboss.com/jira/browse/JBBUILD-335 Project: JBoss Build System Issue Type: Feature Request Components: JBossRetro, Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: JBossBuild-1.1 RC1 In order for maven to build the retro versions of various projects, it would be nice to have a maven plugin version of JBossRetro. -- 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

19 years, 4 months

2
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-831) REQUIRES_NEW is supported for MDBs - not allowed by spec

by William DeCoste (JIRA)

REQUIRES_NEW is supported for MDBs - not allowed by spec -------------------------------------------------------- Key: EJBTHREE-831 URL: http://jira.jboss.com/jira/browse/EJBTHREE-831 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste Per spec, "For a message-driven bean's message listener methods (or interface), only the REQUIRED and NOT_SUPPORTED TransactionAttribute values may be 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

19 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1292) create daily build of portal doc

by Prabhat Jha (JIRA)

create daily build of portal doc -------------------------------- Key: JBPORTAL-1292 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1292 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Prabhat Jha Assigned To: Prabhat Jha Just like daily build of portal trunk is made available for download, daily build of portal doc needs to be made avaialbe. -- 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

19 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4003) using run-as causes anonymous principal to be propagated across EARs and security domains

by Michal Borowiecki (JIRA)

using run-as causes anonymous principal to be propagated across EARs and security domains ----------------------------------------------------------------------------------------- Key: JBAS-4003 URL: http://jira.jboss.com/jira/browse/JBAS-4003 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Michal Borowiecki Using run-as causes anonymous principal to be propagated across EARs and security domains. I have a MDB in EAR 1 with run-as configured. It calls a session bean in the same EAR and the reported identity in the target session bean's method is anonymous, which is OK. The session bean then calls another session bean in another EAR which is in a different security-domain. A ClientLoginModule is used to authenticate in the other security domain. Nevertheless, the target bean sees the caller as anonymous, with the role configured as run-as in EAR1. The same code works OK when run-as is removed from configuration. I understand that the run-as role with anonymous identity is propagated across subsequent ejb calls, however it should not be propagated when explicit login is used on some other security domain. After all, the whole point of authenticating into a security domain is to establish an identity in that domain. It seems that the newly established identity is ignored in favour of the run-as identity and role propagated from the original security domain. -- 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

19 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-578) Running Jboss Rules in Weblogic

by Ruban Mahendran (JIRA)

Running Jboss Rules in Weblogic ------------------------------- Key: JBRULES-578 URL: http://jira.jboss.com/jira/browse/JBRULES-578 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Environment: Running JBoss Rules in Weblogic8.14 via a JSP deployed in a WAR. Reporter: Ruban Mahendran Assigned To: Mark Proctor When attempting to create a package from a class called by a JSP ( see below) I get the following error: CharScanner; panic: ClassNotFoundException: org.antlr.stringtemplate.language.ChunkToken Stopping the Weblogic Workshop debugger... Debugger Stopped. The Weblogic server stops as well. Here is the code snippet called by the jsp PackageBuilderConfiguration pkgBuilderCfg = new PackageBuilderConfiguration(); pkgBuilderCfg.setCompiler(PackageBuilderConfiguration.JANINO); PackageBuilder builder = new PackageBuilder(pkgBuilderCfg); builder.addPackageFromDrl((new InputStreamReader(new FileInputStream("c:\\myruleresource.drl")) ) ); -- 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

19 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-985) build failed under jboss distribution

by Ben Wang (JIRA)

build failed under jboss distribution ------------------------------------- Key: JBCACHE-985 URL: http://jira.jboss.com/jira/browse/JBCACHE-985 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ben Wang Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 After doing a "build dist" under JBC, do an unzip of the JBossCache-xxx.zip, and then do a "build compile" would fail to compile becuase new dependency on ant and some cacheloader (bdbje) errors. -- 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

19 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4077) Full programtic login integration with web container

by Scott M Stark (JIRA)

Full programtic login integration with web container ---------------------------------------------------- Key: JBAS-4077 URL: http://jira.jboss.com/jira/browse/JBAS-4077 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1, JBossAS-4.2.0.CR1 Reporter: Scott M Stark Assigned To: Anil Saldhana We should provide the full hooks to trigger login from web components. -- 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

19 years, 4 months

2
3
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 February 2007