July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2075) CMS failure in jboss-portal-ha when LDAP is used for authentication

by Martin Putz (JIRA)

CMS failure in jboss-portal-ha when LDAP is used for authentication ------------------------------------------------------------------- Key: JBPORTAL-2075 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2075 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.5 SP1 Environment: OpenDS as LDAP server Reporter: Martin Putz Assignee: Sohil Shah 1. Used JBoss AS EAP 4.3 with all configuration (profile) and deployed JBoss Portal 2.6.5 HA Bundle on top of it. 2. Configured portal to use OpenDS (LDAP) for user, role and membership information. 3. Started up both the cluster nodes and logged in to Portal 4. Created a new instance of default CMSWindow and added a security protected CMS resource to it. ( e.g. /default/content/private/license.html) Added this new instance of CMSWindow to the default portal page. 5. When I visit the default portal page (on node1) ( home page ), if user is logged in, the protected resource aka the license.html is shown and if the user is not logged in Access denied message is shown instead of the CMSWindow2 content. So far everything is fine and as expected. 6. When the default portal page (on node2) is accessed without a user being logged in, a '404 Page Not found' is shown instead of the 'Access denied message' 7. With user being logged in, now shut down the active node that was being accessed over a load balancer. Hit refresh or visit the portal again. Result: User is not asked to login again as the session is correctly replicated. However, for the protected CMS resource a "404 Page Not found" is shown. Everything works fine if the User,Role information is coming from database store. It looks like in case of LDAP store the security (aka Role information ) is not available on the replicated cluster node. -- 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

18 years

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1726) Failed status of service factories is not always properly managed.

by Chris Laprun (JIRA)

Failed status of service factories is not always properly managed. ------------------------------------------------------------------ Key: JBPORTAL-1726 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1726 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.2 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.3 Final, 2.8 Final -- 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

18 years

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-5777) Ejb3AuthenticationInterceptor should propagate the GeneralSecurityException

by Marcus Moyses (JIRA)

Ejb3AuthenticationInterceptor should propagate the GeneralSecurityException --------------------------------------------------------------------------- Key: JBAS-5777 URL: https://jira.jboss.org/jira/browse/JBAS-5777 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-4.2.3.GA Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: JBossAS-4.2.4.GA The handleGeneralSecurityException(GeneralSecurityException) method just logs the GSE and throws an EJBAccessException. The GSE should be set as the cause of the EJBAccessException. -- 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

18 years

1
1
0 / 0

[JBoss JIRA] Resolved: (JBWEB-59) Automatically configuring mod_jk uri's

by Remy Maucherat (JIRA)

[ https://jira.jboss.org/jira/browse/JBWEB-59?page=com.atlassian.jira.plugi... ] Remy Maucherat resolved JBWEB-59. --------------------------------- Fix Version/s: JBossWeb-2.1.1.GA Resolution: Done AS 5 will include mod_cluster, which is a fancier solution. > Automatically configuring mod_jk uri's > -------------------------------------- > > Key: JBWEB-59 > URL: https://jira.jboss.org/jira/browse/JBWEB-59 > Project: JBoss Web > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Module > Reporter: Vicky Kak > Assignee: Remy Maucherat > Fix For: JBossWeb-2.1.1.GA > > > Tomcat provides a feature to automatically generate the mod_jk configuration based on which web applications are deployed: > http://svn.apache.org/repos/asf/tomcat/connectors/trunk/jk/java/org/apach... > However, this feature does not seem to work with the embedded Tomcat. I was wondering: > 1) Is there a way to get this feature to work? > 2) Better yet, is there another recommended mechanism to keep the mod_jk configuration in sync with the deployed applications? > My concern is that if we begin hosting static content via apache, or if we need apache to have multiple modules loaded in apache, some request dispatching via mod_jk and others dispatching via other mechanisms, we will then have to manually maintain update a mod_jk.conf file (or uriworkermap.properties). -- 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

18 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWEB-83) When the native libraries are missing it is not possible to use ajp

by Jean-Frederic Clere (JIRA)

When the native libraries are missing it is not possible to use ajp ------------------------------------------------------------------- Key: JBWEB-83 URL: http://jira.jboss.com/jira/browse/JBWEB-83 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.1 GA Environment: Any Reporter: Jean-Frederic Clere Assigned To: Mladen Turk When the ./bin/native/libtcnative-1.so or one of the components of Jboss Web native is missing. The ajp connector is defaulted to a http one: +++ 17:37:05,565 ERROR [AprLifecycleListener] The Apache Tomcat Native library that JBoss Web requires (only the HTTP connector will be available) was not found on the java.library.path: /home/jfclere/TMP/jbossweb-1.0.1.GA/bin/native 17:37:05,636 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 17:37:05,637 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8009 +++ -- 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

18 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWEB-66) basic-auth broken

by Mark Stewart (JIRA)

basic-auth broken ----------------- Key: JBWEB-66 URL: http://jira.jboss.com/jira/browse/JBWEB-66 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.0 GA Environment: Linux Reporter: Mark Stewart Assigned To: Mladen Turk Assuming that Jboss Web is configured identically to the web container in AS, it seems that basic-auth support is broken. That is, the server doesn't send a 401 for protected urls. Here's the post I made three weeks ago on the Jboss Web Server forum: "I have a webapp I usually run in JBoss AS that I'm trying to get running under JBossWeb. I've added the same entry to login-module.xml in the default/conf/ directory and a jboss-web.xml file whose <security-domain> tag points at the entry in default/deploy/<my-web-app.war>/WEB-INF. JBossWeb doesn't block the access to the protected pages, however." This is tested by the J2EE CTS so I guess JBossWeb wasn't tested against it (or the failure was ignored) prior to the GA release. -- 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

18 years

3
2
0 / 0

[JBoss JIRA] Created: (JBWEB-73) Context defined in the server.xml of the jbossweb.sar does not get installed properly .

by Vicky Kak (JIRA)

Context defined in the server.xml of the jbossweb.sar does not get installed properly . --------------------------------------------------------------------------------------- Key: JBWEB-73 URL: http://jira.jboss.com/jira/browse/JBWEB-73 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBoss Web Server 1.0.1 GA Reporter: Vicky Kak Assigned To: Mladen Turk The context element defined in the server.xml of the jbossweb.sar is not honored . The context defined in the server.xml are not deployed when the Tomcat boots , this works properly with standalone Tomcat and Jboss AS . -- 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

18 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWEB-98) Need better support over JspRuntimeContext class loader assumptions

by Scott M Stark (JIRA)

Need better support over JspRuntimeContext class loader assumptions ------------------------------------------------------------------- Key: JBWEB-98 URL: http://jira.jboss.com/jira/browse/JBWEB-98 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Mladen Turk The JspRuntimeContext is assuming it has access to a URLClassLoader. This is not true for jbossas5. -- 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

18 years

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5722) Get all the testsuite passing

by Dimitris Andreadis (JIRA)

Get all the testsuite passing ----------------------------- Key: JBAS-5722 URL: http://jira.jboss.com/jira/browse/JBAS-5722 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Shelly McGowan Priority: Blocker Fix For: JBossAS-4.2.3.GA Parent issue to link all testsuites that we need to check/fix -- 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

18 years

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5726) Verify JBossWS testsuite

by Dimitris Andreadis (JIRA)

Verify JBossWS testsuite ------------------------ Key: JBAS-5726 URL: http://jira.jboss.com/jira/browse/JBAS-5726 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Shelly McGowan Priority: Critical Fix For: JBossAS-4.2.3.GA Verify we are good with the JBossWS testsuite (which one? ) -- 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

18 years

4
14
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 July 2008