what about simply reusing the userlist from the cocoon-dev, cocoon-user, cocoon-doc mailing lists and allow write access only to these
registered users ?
We don't have access to the list of registered email addresses on cocoon-* lists, and I doubt that will happen any time soon - there's some privacy issues involved with that, too.
Pier, do you have any opinion about this?
I'm thinking along the lines of adding some container-based authentication around Edit.jsp, and some smallish webapp so that people can register an email address (= user name) / password. Does anyone has something like that laying around? Use cases:
* enter email address -> generated pwd gets send to you
-> address & pwd are stored in db
* you can log into that app
-> change pwd
-> drop your registration data
* that same database is used for container-based authentication around Edit.jsp
What do you guys think?
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
