> >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 ? > > None ;-) > > RIFE authentication is totally based on behavioral inheritance > (inherits declaration). > > To write an element for HTTP authentication I would just extend > Element and start from scratch, using the managers in the > authentication package. Much of the logic in the extending elements > are related to forms, html, cookies and query parameters.
welll ehhh so the authent'n element simply either blocks the URL or passes it ? Is that the idea ? When it gets the identity, it merely sets a cookie or a global variable ? Is there a subclass or a basic Impl -class that does a lot of this ? fred _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
