DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35466>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35466


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |trivial
           Priority|P2                          |P4




------- Additional Comments From [EMAIL PROTECTED]  2005-06-23 10:25 -------
Headnote: reading your bug report left me with the feeling you are someone who  
 
doesn't understand the basics of J2EE environnement and is blaming people for   
his ignorance, I simply don't like such behaviour. I admit the doc is not  
always clear, but if you need hints on how to configure slide on your tomcat,  
you'll better have posted your question the mailing list. And for the sake, if  
you don't know how to configure a j2ee container and just want a ready to run  
WEBDAV server, download the tomcat bundle version of slide.  
   
- First, enabling authentification for slide in web.xml does not mean slide     
   
does the authentification, this only mean access to DAV servlet will require    
     
authentification from container (see any J2EE basic documention on web.xml      
  
auth-constraint section) 
         
- Second, as stated in      
http://jakarta.apache.org/slide/howto-create-users.html, <<I believe this      
depends upon you having the Slide Realm as the default authentication      
mechanism for Slide. This is the default if you have installed the Tomcat      
bundle.>> So you are following a doc which refers to using the Slide-Realm,     
 
not the default tomcat realm (tomcat-user.xml is the default tomcat-realm) and 
which was written by someone who used the tomcat-bundle    
     
- Thirds, as indicated in http://jakarta.apache.org/slide/howto-acl.html, the   
 
realm wrappers.catalina.SlideRealm does the link between slide user and the    
tomcat users.    
    
    
/users/* and /roles/* are used by slide to manage it's ACLs, that is the     
webdav authorisations part. If you want to use slide to do the     
authentification too, you need to follow the instructions at     
http://wiki.apache.org/jakarta-slide/SlideRealm      
    
I quote you: "In actuality, it is the tomcat-users.xml file that actually    
creates users recognized by Slide. The users, passwords, and roles entered    
into that file determine who can log in and what their permissions are."    
That is false, in your configuration, tomcat-users.xm define authentification   
 
and authorization managed by CONTAINER, If you add users only there, tomcat    
will not grant them any right accoring to acl as there is no    
corresponding /user/    
    
    
I'll recommend you learn a bit how security work with servelts and J2EE    
containers before you starting blaming slide docs. Explaining the J2EE    
sepecifications is out of the scope of slide documentation,    
    
    
Though i admit there are some ambiguities in    
http://jakarta.apache.org/slide/howto-create-users.html were this should be    
stated explicitly that you need slide realm.     
    
Also in http://jakarta.apache.org/slide/howto-acl.html the sentence "By    
default, when running inside Tomcat, authentication for the WebDAV servlet is   
 
controlled by the realm wrappers.catalina.SlideRealm which accesses user names  
  
and passwords directly from the Slide namespace at /slide/users."     
should be replaced by "By default, when running inside Tomcat-bundle,    
authentication for the WebDAV servlet is controlled by the realm    
wrappers.catalina.SlideRealm which accesses user names and passwords directly   
 
from the Slide namespace at /slide/users." 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to