October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4747) WebAuthentication programmatic login prevents the user from ever logging out

by Matt Cristantello (JIRA)

WebAuthentication programmatic login prevents the user from ever logging out ---------------------------------------------------------------------------- Key: JBAS-4747 URL: http://jira.jboss.com/jira/browse/JBAS-4747 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.2.1.GA Environment: CentOS 3, JDK 1.5.0_12, JBoss Portal 2.6.1.GA with JBoss AS 4.2.1.GA, set up in ClusteredSingleSignOn mode Reporter: Matt Cristantello Assigned To: Scott M Stark When using the WebAuthentication login(String,String) method, it is not possible to log out even if the logoff() method of the WebAuthentication is called. Code: auto_login.jsp <%@page import="org.jboss.web.tomcat.security.login.WebAuthentication"%> <% WebAuthentication pwl = new WebAuthentication(); pwl.login("user", "user"); response.sendRedirect("test.jsp"); %> logout.jsp <%@page import="org.jboss.web.tomcat.security.login.WebAuthentication"%> <% WebAuthentication pwl = new WebAuthentication(); pwl.logout(); %> <p>Successfully logged out</p> test.jsp <html> <head> <title>Test Page</title> </head> <body> <p>Username: <%=request.getRemoteUser() %></p> <p><a href="logout.jsp">Log Out</a></p> </body> </html> web.xml <?xml version="1.0" encoding="UTF-8"?> <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> <display-name>test</display-name> <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> <welcome-file>default.html</welcome-file> <welcome-file>default.htm</welcome-file> <welcome-file>default.jsp</welcome-file> </welcome-file-list> <security-constraint> <web-resource-collection> <web-resource-name>test</web-resource-name> <url-pattern>/test.jsp</url-pattern> <http-method>POST</http-method> <http-method>GET</http-method> </web-resource-collection> <auth-constraint> <description>Authentication required</description> <role-name>Authenticated</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>FORM</auth-method> <realm-name>JBoss Portal</realm-name> <form-login-config> <form-login-page>/login.jsp</form-login-page> <form-error-page>/error.jsp</form-error-page> </form-login-config> </login-config> <security-role> <role-name>Authenticated</role-name> </security-role> </web-app> jboss-web.xml <?xml version="1.0"?> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd"> <jboss-web> <security-domain>java:jaas/portal</security-domain> </jboss-web> Steps: 1. Log in by navigating to auto_login.jsp 2. Click the log out link, or otherwise navigate to the logout.jsp page. 3. Navigate back to the test.jsp page. You will still be logged in. This problem also occurs with the JBoss Portal 2.6.1, where I am automatically logged into the JBoss portal after running auto_login.jsp, but I cannot log out of the Portal using its logout button or the logout.jsp provided as an example above. I am not seeing any entries in my server.log files when the logout methods are called, even with debug messages being logged. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1035) get latest tutorials online

by William DeCoste (JIRA)

get latest tutorials online --------------------------- Key: EJBTHREE-1035 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1035 Project: EJB 3.0 Issue Type: Task Reporter: William DeCoste Assigned To: William DeCoste -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-639) AS Integration

by Ovidiu Feodorov (JIRA)

AS Integration -------------- Key: JBMESSAGING-639 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-639 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 Container task for anything related to integration. -- 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 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-641) Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance

by Ovidiu Feodorov (JIRA)

Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance -------------------------------------------------------------------- Key: JBMESSAGING-641 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-641 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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 months

5
11
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Clebert Suconic closed JBMESSAGING-388. --------------------------------------- Resolution: Done JBM already cover migration (just look at installation docs) > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: AS 5.0 Integration > > -- 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 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Clebert Suconic closed JBMESSAGING-388. --------------------------------------- Resolution: Done > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Fix For: AS 5.0 Integration > > -- 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 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Clebert Suconic reopened JBMESSAGING-388: ----------------------------------------- Assignee: Clebert Suconic > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: AS 5.0 Integration > > -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1731) Document / Tutorial Data Display from Database using Hibernate

by Eric Brennan (JIRA)

Document / Tutorial Data Display from Database using Hibernate -------------------------------------------------------------- Key: JBPORTAL-1731 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1731 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Reference Guide Affects Versions: 2.6.2 Final Environment: Portal 2.6.1 GA Oracle backend. Reporter: Eric Brennan Assigned To: Julien Viet Priority: Optional It would be nice to have a tutorial on Displaying records from a Database using hibernate. Could expand the Helloworld example to pull two fields from a database. How to configure Hibernate CFG so that it pulls a generic DS. Nice to have records displayed bases on login ID. -- 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 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-324) Facility for real-time decision on best InvokerLocator by which to contact a given handler.

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-324?page=comments#action_12379624 ] David Lloyd commented on JBREM-324: ----------------------------------- The Routing/Discovery API of Remoting 3 should facilitate this ability, if I understand correctly. It will maintain a list of paths to endpoints, and choose the best one available at any given time. > Facility for real-time decision on best InvokerLocator by which to contact a given handler. > ------------------------------------------------------------------------------------------- > > Key: JBREM-324 > URL: http://jira.jboss.com/jira/browse/JBREM-324 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.0.0.Beta1 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Priority: Minor > Fix For: 4.0.0.Beta1 > > > The basic idea is to be able to communicate with a single handler by way of different InvokerLocators. For example, if you're working over the internet, compression might be advantageous, but if you're local it might not be. So you could have two Connectors sharing a handler, one using the compression marshaller and one not. > How about a client that > 1. gets the InvokerLocators for all of the Connectors for a certain handler, via a detector, > 2. sends some sample invocations to each and times them, and > 3. displays the results. > It could be used for real time decision making or to collect information for a set of rules. -- 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 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-305) Provide support for JMS transport

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379620 ] David Lloyd commented on JBREM-305: ----------------------------------- Thomas, are there any specific requirements regarding the format of the JMS message? Or do you just want your message to be moved from one endpoint to another? > Provide support for JMS transport > --------------------------------- > > Key: JBREM-305 > URL: http://jira.jboss.com/jira/browse/JBREM-305 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 beta > Reporter: Thomas Diesler > Assigned To: Tom Elrod > Fix For: 4.0.0.Beta1 > > > The web service layer has a need for JMS transport -- 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 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007