Results 1 to 4 of 4

Thread: WebDAV home folders authorization

  1. #1
    Join Date
    Dec 2005
    Posts
    16

    Default WebDAV home folders authorization

    Hello dear forum members.

    I'm wondering what is the best way to secure access to WebDAV server to provide functionality similar to user "home" folders, that is, user "a" should have full access rights to /a/*, user b to /b/* , etc. I'd like to use digest authentication filter on top webdav server (either slide or jackrabbit) and have separate authentication realm for each user. Current implementation of Digest Entry Point allows only static configuration of realm; Should I subclass DigestEntryPoint to achieve my goal?

    Also, my question to Ben - as I've seen in forum history, you were going to create separate project for spring and webdav integration, so I can assume you solved similar kind of problem. Maybe a bit offtopic, what do you think, does jackrabbit has enough quality to be used in a production system as a webdav repository and server or it's better to use slide? The main problem I see with slide is lack of significant development activity since 2004 year and bad documentation.

  2. #2
    Join Date
    Dec 2004
    Location
    Minneapolis, MN
    Posts
    20

    Default

    I'm interested in Acegi/WebDav as well.

    -Todd

  3. #3
    Join Date
    Dec 2004
    Location
    Minneapolis, MN
    Posts
    20

    Default

    I found this link helpful in my search-

    http://www.mail-archive.com/slide-us.../msg05881.html

    Ben talks about integrating Acegi, CAS and Jakarta Slide.

    Ben, I'm curious if any your thoughts have changed since that time?

  4. #4
    Join Date
    Aug 2004
    Location
    Sydney, Australia
    Posts
    2,768

    Default

    I have not been monitoring how Slide or Jackrabbit are progressing as projects.

    My needs with WebDAV were quite simple, so in the end I used Tomcat's WebDAV Servlet and then popped a Filter in front of it. The filter used Acegi Security's SecurityContextHolder to determine who the user is. It then checked the path the user was requesting from the WebDAV servlet, and sent back a redirect to their home directory if they were trying to access someone else's directory. It was simple, but worked fine. And I didn't need to implement a complex WebDAV server for this particular application's content management needs.
    Ben Alex
    Project Founder, Spring UAA, Spring Roo and Spring Security

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •