Eduard Witteveen wrote: > The misusage of other names in the taglibs is either a bug in the > taglibs, or _all_ implementations of the security.
I'm tempted to say it's a taglib bug, but really it doesn't matter. Taglib is what users use, so the names (in the users view) should match. The alternative is to add the username/password as complete attribute names to the cloud tag (as alternative attributenames). Also you need to adjust the documentation slightly if you allow othe authentication methods: *** If the page was called with the 'command' parameter set to 'login', the tag assumes a request is being made to log on using the parameters passed. Teh actual names of the parameter spassed differs by security method chosen, which is defined by the 'authenticate' attribute. For instance, with authenticate method 'username/password', the following additional parameters are recognized: name: similar to the cloudtag's 'name' attribute username: similar to the cloudtag's 'logon' attribute password: similar to the cloudtag's 'pwd' attribute *** -- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "All your MMBase are belong to us"
