Of course, Ben would be the most qualified to answer your questions, but I'll take a shot at it from my (more limited) experience with Acegi. The way Acegi typically works, as you know, is to authenticate the user in the filter level before your WebDAV servlet is invoked. However, you say that you do not want to authenticate at the filter level. Maybe you could elaborate on your reasons? I've still got a hazy picture of exactly how Jackrabbit is put together, so you might be seeing something that I'm not. I could guess that maybe JCR-170/Jackrabbit is going to authenticate the user via JAAS, so you want to avoid authenticating the user via Acegi as well? It sounds like what you are saying is that you want to extract the credentials (maybe via Acegi) up front (without authenticating), and then pass those credentials to Jackrabbit, which will then proceed to authenticate them via JAAS. Am I understanding this correctly? I could see this becoming tricky when it comes to digest authentication, as the client is sending the server a digest and not the user's actual credentials. At this point, I'm thinking that I should make sure my understanding of things is correct before writing more, as I don't want to waste any time writing a response to a misunderstood question, if that's the case. :)
- Andy ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Acegiwebdav-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegiwebdav-developer
