Hmm, > >The WebDAV-enabled editor is not going to grok Rife authentication. > >So let's say I configure Tomcat to use standard HTTP authentication > >to protect that URL space. Then I have to keep Tomcat's user file > >tomcat-users.xml in sync with Rife (unless I come up with a miracu- > >lous hack). > > > >Also, then, when the WebDAV user is authenticated, and the request > >is passed to my Rife app, I wonder how I can access the Tomcat > >authentication data. > > > >I know this is a quite complex subject. I have the book "Professional > >Apache Tomcat 5" (Wrox) and I've scanned the Tomcat docs and it's > >quite a tangle. > > It should not be difficult to write HTTP authentication using RIFE's > authentication API. It should also be possible to plug into Tomcat's > authentication. This would be a cool way to contribute to the project!
If I look at the inheritance tree for (say) com.uwyn.rife.authentication.elements.PurgingMemoryAuthenticated it's fairly deep (see below). Exactly which class has to be extened -- or which interface has to be implemented -- to make an authentication provider ? fred http://rifers.org/docs/api/com/uwyn/rife/authentication/elements/PurgingMemoryAuthenticated.html com.uwyn.rife.authentication.elements Class PurgingMemoryAuthenticated java.lang.Object extended by com.uwyn.rife.engine.ElementSupport extended by com.uwyn.rife.engine.Element extended by com.uwyn.rife.authentication.elements.Identified extended by com.uwyn.rife.authentication.elements.Authenticated extended by com.uwyn.rife.authentication.elements.RoleUserAuthenticated extended by com.uwyn.rife.authentication.elements.MemoryAuthenticated extended by com.uwyn.rife.authentication.elements.PurgingMemoryAuthenticated All Implemented Interfaces: SessionAttributes, ElementAware, Cloneable _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
