Those should be set as base_config.sa_auth.dbsession and base_config.sa_auth.user_class inside your application config/app_cfg.py and are normally consumed by SQLAlchemy and Ming repoze.who authenticators. If you are using your own authenticators you can safely remove them from app_cfg.py, that should solve your issue.
On Thu, Aug 15, 2013 at 5:55 PM, MHCPU <[email protected]> wrote: > Hi, > > By following the documentation "Authentication in TurboGears2 > applications" and "About repoze.who Plugins" I've written an authenticator > plugin and a metadata provider plugin for LDAP. There is one thing I had > to change in TG2.3beta2 to make this work. This could be a bug, or I could > be doing something wrong. > > In lib/python2.6/site-packages/tg/configuration/auth/setup.py I had to > remove the keys 'dbsession' and 'user_class' from who_args: > > dbsession = who_args.pop('dbsession', None) > user_class = who_args.pop('user_class', None) > > otherwise lib/python2.6/site-packages/repoze/who/middleware.py would > complain about unexpected keywords arguments. > > Matthew > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/groups/opt_out.
