incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harry Metske (JIRA)" <>
Subject [jira] Updated: (JSPWIKI-389) Container managed login fails with Geronimo
Date Fri, 03 Oct 2008 15:10:44 GMT


Harry Metske updated JSPWIKI-389:

    Attachment: JSPWIKI-389.patch

First, I'm not a Geronimo expert.
Did you invoke the admin/SecurityConfig.jsp? This is a very useful tool for diagnosing these
kind of problems.
If you run that you first have to allow it by adding    jspwiki-x.securityconfig.enable=true
   to the file.

I checked it myself, and ran into a JSP compile error for it (Geronimo is more strict that
Tomcat, I will fix that in the repo separately, but the patch is attached in case you need
it earlier).

Then you should check your Geronimo realms and the and
file that are probably pointed to by it.
Another thing I noticed (not sure if that matters), is that in your deployment plan above
you specified admin in lowercase twice, shouldn't the first one be Admin ?

> Container managed login fails with Geronimo 
> --------------------------------------------
>                 Key: JSPWIKI-389
>                 URL:
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Authentication&Authorization
>            Reporter: J├╝rgen Weber
>             Fix For: 3.0
>         Attachments: JSPWIKI-389.patch
> I tried JSPWiki v2.8.0-beta-10  on Geronimo 2.1.3 (Sun 1.6.0_07 on Ubuntu 8.0.4)
> JSPWiki comes up fine, but when I try to log in, the
> http://linda:8080/JSPWiki/Login.jsp?redirect=Main
> is forbidden.
> jspwiki.policy unchanged, web.xml uncommented container managed security, geronimo-web.xml
as below.
> Apache JSPWiki should work on Apache Geronimo.
> ------------
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="" 
>          xmlns:naming="" 
>          xmlns:sec="" 
>          xmlns:sys="">
>   <security-realm-name>jspwiki-properties-realm</security-realm-name>
>   <sec:security>
>     <sec:role-mappings>
>       <sec:role role-name="Authenticated">
>         <sec:principal class=""
name="Authenticated" designated-run-as="true"/>
>       </sec:role>
>       <sec:role role-name="admin">
>         <sec:principal class=""
name="admin" designated-run-as="true"/>
>       </sec:role>
>     </sec:role-mappings>
>   </sec:security>
> </web-app>

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

View raw message