Hi Alexander,
Il giorno mer, 15/06/2011 alle 09.33 +0200, Alexander Wagner ha scritto:
> > If you were using both local and LDAP (unless there's some
> > bug), you could have authenticate with any of the two.
>
> That's the point. In fact I allow both, though the default
> is LDAP. (The idea is that we might have users that do not
> have a local mail address.)
>
> > (In the login form you could have seen, under the username
> > and password field, a dropdown menu letting you choose
> > between local and LDAP authentication.
>
> Right. There seems, however, no equivalent in the CLI-tools,
> right? Ie. no parameter except -u.
so are you then talking about launching bibtasks at the prompt? In that
case indeed it is used the default authentication method you choose (in
the past it was always used the local authentication to authorize
bibtasks, but the very developer and contributor of the LDAP plugin also
proposed we should use whatever authentication method is set as
default).
IMHO, it has come the time when we can simply remove any authentication
level when starting bibtasks from the command line. Any way if you can
access the server via SSH and starts a Python prompt you can easily
bypass these security checks, so we might simply remove this
authentication step which is just a burden for the admin. (while still
keeping the -u/--user argument for bibtasks so that it is possible to
log who requested a certain task).
Cheers,
Sam
--
Samuele Kaplun
Invenio Developer ** <http://invenio-software.org/>
