Hi Bart, Anyone else feel free to correct me if I'm wrong on the following:
The wedav spec requires the users and roles to be present in webdav. The J2EE spec doesn't require users and roles to be present. A J2EE server has to able to authenticate but you can't get a list of users and roles from a J2EE server through the J2EE apis. So you can't tie the webdav and j2ee security models together this way. Ideally, I think, you would want to write a webdav store to retrieve the users and roles from the same place that your J2EE server currently gets it's users and roles from. You would then mount the webdav users and roles directiories in such a way as to use your new store and set up your J2EE server to use slide for authentication. However there is an easier solution that is not quite so neat. Slide has auto-create-user functionality that will automatically set users up in slide that have been authenticated by your J2EE server. However this functionality is currently broken. I submitted a patch to fix this problem a few weeks ago for version 2.0rc1 but it required some more work. I will have a patch available shortly for version 2.0. I haven't tried but you might be able to apply it to version 2.0 if you're desperate. The original patch is at: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05674.html Jamie. -----Original Message----- From: Bart Molenkamp [mailto:[EMAIL PROTECTED] Sent: 06 May 2004 08:53 To: [EMAIL PROTECTED] Subject: Using the J2EE containers users and roles Hello, Is it possible to use the roles provided by a J2EE container to secure the repository (where Slide somehow uses the isUserInRole(...) method of the HttpRequest, instead of the roles in the repository under /roles)? E.g. if there is some permission for /roles/root, Slide will do isUserInRole("root") or something similair. Thanks, Bart. _________________________________________________________________ MSN Search, for accurate results! http://search.msn.nl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
