portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sean Taylor (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-828) JAAS authentication failure with Tomcat 5.5.24 and above.
Date Tue, 24 Jun 2008 23:31:46 GMT

     [ https://issues.apache.org/jira/browse/JS2-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Sean Taylor resolved JS2-828.

       Resolution: Fixed
    Fix Version/s: 2.2

By setting the context.xml "useContextClassLoader" attribute = true, this is now working in

 <Realm className="org.apache.catalina.realm.JAASRealm"

I just commited a patch to the context.xml

I am considering this issue resolved now. I have not tested on Glassfish or Tomcat 6
Please create new issues for Glassfish and Tomcat 6 if the problem exists there

> JAAS authentication failure with Tomcat 5.5.24 and above.
> ---------------------------------------------------------
>                 Key: JS2-828
>                 URL: https://issues.apache.org/jira/browse/JS2-828
>             Project: Jetspeed 2
>          Issue Type: Bug
>         Environment: Tomcat >= 5.5.24
>            Reporter: Mohan Kannapareddy
>            Assignee: Ate Douma
>            Priority: Critical
>             Fix For: 2.2
> Immediately after logging into the portal, the URL address box in the browser displays:
>  http://localhost:20000/jetspeed/login/redirector
> ======================
> And the page displays:
> HTTP Status 403 - Access to the requested resource has been denied
> type Status report
> message Access to the requested resource has been denied
> description Access to the specified resource (Access to the requested resource has been
denied) has been forbidden.
> Apache Tomcat/5.5.25
> ======================
> I believe this is the same behavior in Tomcat 6.0.x and I get the same thing in GlassFish
> This does *NOT* happen in Tomcat 5.5.23 or lower versions. Something changed between
5.5.23 and 5.5.25.
> Also, after the login post if you just type in the URL http://<>/jetspeed, the
page appears normally and you can
> function.
> I do not know whether it is relevant but at least GlassFish appears to record the following
in the server.log.
> Unable to set request character encoding to UTF-8 from context /jetspeed, because request
parameters have already been read, or ServletRequest.getReader() has already been called

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message