[sakai2-tcc] Commentary/Followup on the captcha vote. Some misleading SAK's

[Matthew Jones]

Also, as a followup on this issue,

I had no problem with the patch made against after the freeze for new
accounts in SAK-12489 <http://jira.sakaiproject.org/browse/SAK-12489> but
was slightly concerned with the one that was claimed to be made before the
freeze for login in SAK-13297<http://jira.sakaiproject.org/browse/SAK-13297>
.

At a quick glance, they both *seemed* to use different methods for captcha.
Upon further investigation, there actually is no captcha support for
(failed) logins in the code, and SAK-13297 is actually the same as SAK-12841
(turning the login page into a VM template). So the only SAK that involves
captcha at all is the first.


Things I'd like to see happen:
* Both really should use the same library for capcha
* You should be able to use one without the other (different properties)

Since login doesn't actually implement captcha, this really isn't an issue
at the moment.

*(User accounts)*
SAK-12489 uses the *net.tanesha.recaptcha4j* library and toggled with the
property recaptcha.enabled=true. This property should be called
user.recaptcha.enabled in the alpha now (and the other similar properties
also prefixed with user).

(Login)
I don't actually *see* anything in SAK-13297 that adds captcha to login.
There was commentary about using a gatekeeper contrib project in the, but it
looks like this entire change was just related to turning the login page
into a VM template (SAK-12841) and doesn't implement what the title claims.
Captcha's for login (if implemented) should use the same library/method and
be pushed back until 2.9 (or at least 2.8.1 since they aren't don't even
seem to be implemented yet.

When done, I'd make them under a new property as you might new user capcha's
and not account failure captcha's  (login.recaptcha.enabled)

-Matthew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100930/1fbbb6a4/attachment.html