Thanks for the answers so far.
It is ok for me to use both authentification mechanisms for the whole site.
So I did the following in app_cfg:
from repoze.who.plugins.auth_tkt import AuthTktCookiePlugin
from repoze.who.plugins.basicauth import BasicAuthPlugin
authtkt = AuthTktCookiePlugin('authtkt', 'authtkt')
basicauth = BasicAuthPlugin("something")
base_config.sa_auth.identifiers = [ ('repoze.whoplugins.basicauth', basicauth
), ('repoze.whoplugins.auth_tkt',authtkt)]
base_config.sa_auth.form_plugin = None
It seems to be working. I'll do some more testing tomorrow and try to
understand why it does so ;-)
Thanks again,
Christian
Am 03.03.2011 um 17:52 schrieb Alessandro Molina:
>>>
>>
>> No, repoze.who is certainly capable of that. But I don't know how exactly - I
>> always get lost in the classifier, challenger identifier and
>> meta-data-provider
>> thingies.
>
> The identifiers, authenticators and challengers options of the repoze
> middleware should be a list of pluggable pieces that should be checked
> one after the other for being able to identify/authenticate the user.
>
> Registering both the auth tkt and basic auth identifiers should
> provide authentication for both. I don't know it is possible to do
> that basing on the url, but you can surely enable both for the entire
> application.
>
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en.
