Thank you. I would not have figured that out.
When I set base_config.sa_auth.authmetadata = None, I see a param mismatch
exception when PluggableAuthenticationMiddleware's __init__() is called.
In /tg/configuration/app_config.py::add_auth_middleware()
*if 'authmetadata' not in auth_args:
calls setup_sql_auth() .. consumes permission_class and translations
etc. and in turn calls setup_auth() such that when it calls
PluggableAuthenticationMiddleware() the parameters match
else:
calls setup_auth() with auth_args .. and
PluggableAuthenticationMiddleware() chokes on invalid parameters
permission_class, dbsession, translations, etc.
*
I will debug further..
On Sunday, November 25, 2012 5:26:21 AM UTC-8, Alessandro Molina wrote:
>
> If you remove the base_config.sa_auth.authmetadata field you just disable
> the 2.2 auth layer and fall back to the repoze.what-quickstart one, that is
> why you get the SQLAlchemyUserMDPlugin registered.
>
> To use the the new auth setup but skip the default TG metadata provider
> just set authmetadata to None.
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/turbogears/-/RLce26ZPv3AJ.
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.
