CALL FOR: ASelect Authentication module
Called by: Michiel Meeuwissen Total tally on this call (excluding the caller's vote) : +12
START OF VOTING: 2005-03-11 20:30 END OF CALL: 2005-03-16 20:30
YEA (13) : Rob Vermeulen, Eduard Witteveen, Rob van Maris, Gerard van Enk, Andre van Toly,Daniel Ockeloen, Marcel Maatkamp, Pierre van Rooden, Nico Klasens, Kees Jongenburger, Michiel Meeuwissen, Rico Jansen, Ernst Bunders
ABSTAIN (1) : Mark Huijser
NAY (0) :
VETO (0) :
No votes, assumed abstained (2): Jaco de Groot, Johannes Verelst
*) This vote needs a total tally of +3 votes in addition to any in favor vote of the vote's caller.
Result:
The vote passed. The Aselect securtity application can be added under the 'contributions' cvs module.
Michiel Meeuwissen wrote:
Over a year ago we have developed an MMBase security authentication implementation based on 'A-Select' (see www.a-select.org), initiated by the the Surf foundation (www.surf.nl) and the MMBase foundation, and together with the implementors or A-Select itself alfa & arris (www.alfa-ariss.com).
Recently we have made several improvements on the code, to use it on a web-site for a customer (the province Limburg).
I want to contribute the code as an application in the to-be-created 'third party' CVS module, and will be myself the maintainer.
A-Select is only about user authentication. This part we made a year ago,
only worked together with 'OwerAuthorization'. Recently I implemented a
second option, which makes it possible to use this authorization in
combination with the authorization mechanism of cloud context security.
This creates a compile time dependency on the cloud-context security
application.
The original implementation also depended on the 'A-Select' agent. This is not needed any more, because A-Select itself is also a java web-app, it was easy enough to communicate directly to it, simply by reusing some of its own classes (so a compile time dependency on one of their jars was introduced).
The recent changes on the security framework were mainly initiated by my work on this code. A-Select authentication is completely delegated to a dedicated program so you can never assume e.g. that name/password authentication is acceptable, so because of that the generatlizations were necessary, and are of course now utilized by this code. This is a bit buggy still, but it will be fixed.. At least it provides a test-case for this stuff.
I attach the code. The build.xml still supposes to be in the 'applications' module, but that can be straightened out later, when it is clear how that should be done..
It contains documentation, which is not entirely up-to-date but the configuration is documented in itself.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Anything worth doing is worth overdoing." _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
