Hi Fred,
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.
Best regards,
Geert
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
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
