Needs Doing
* ud-ldap-CGI: Form needs field webpassword
* ud-ldap-CGI: needs processing in update.cgi
* ud-ldap: distribute htpasswd file via ud-generate/ud-replicate

Handlers need to be written:
* ACS_ERROR_HANDLER
* AUTH_SUCCESS_HANDLER
* AUTH_ERROR_HANDLER
* SIGNOUT_HANDLER
prueba

currrently set handlers:
ACS_ERROR_HANDLER    "* https://${Conf::JURISDICTION_AUTHSERVER}/public/index.cgi"
AUTH_SUCCESS_HANDLER "https://${Conf::JURISDICTION_AUTHSERVER}/public/index.cgi"
AUTH_ERROR_HANDLER   "* https://${Conf::JURISDICTION_AUTHSERVER}/public/error.html"
SIGNOUT_HANDLER      "https://${Conf::JURISDICTION_AUTHSERVER}/public/index.cgi"

optionally allow to remove 'autocomplete=off' from the form

Tollef, alioth, postgres, ldap
Message-ID: <87wr1zhi3u.fsf@xoog.err.no>

13:05 #debian-devel < zobel> Lo-lan-do, Mithrandir, sgran: when can we talk about alioth providing oauth2 for 
                             sso.d.o?
13:11 #debian-devel < Lo-lan-do> Whenever. Is there an implementation yet?
13:12 #debian-devel < Lo-lan-do> As it happens, I just developed (for a client) the ability to export 
                                 users/groups/memberships to external databases on the fly via a plugin.
13:13 #debian-devel < Lo-lan-do> The only currently available plugin for that is LDAP, but maybe that would help 
                                 already?
13:18 #debian-devel < enrico> Lo-lan-do: sounds like it would. Alioth feeding a separate LDAP database running on 
                              sso.debian.org, which DACS then binds to
13:18 #debian-devel < enrico> Lo-lan-do: how hard would it be to set that up, alioth-side?
13:19 #debian-devel < Lo-lan-do> Not very. But give me a few days to test the new code first :-)
13:19 #debian-devel < enrico> Lo-lan-do: ok
13:19 #debian-devel < Lo-lan-do> It's not even deployed at the client's yet