I've been trying to work out the best way of making the auth metadata providers be configurable in my app. (Turbogears 2.3.7, Windows, Python 2.7.11)
I have a metadata provider which has the same methods that the ApplicationAuthMetadata class in the file app_cfg.py file has, but they go off and do LDAP stuff in the authenticate, get_user, get_groups, and get_permission methods.
And that all works fine.
However, the existing nosetests fail because they are assuming the manager and editor users that a quick-started app sets up. It's quite useful to maintain this, so I can have a small, repeatable world for these tests.
Is there a way to define the two metadata providers (the regular ApplicationMetadata instance, and my LDAP one) in my app_cfg.py and then select which one of these should be used in the test.ini or development.ini files?
Regards,
Luke
--
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 turbogears+...@googlegroups.com.
To post to this group, send email to turbo...@googlegroups.com.
Visit this group at https://groups.google.com/group/turbogears.
For more options, visit https://groups.google.com/d/optout.
Sent: 13 April 2016 17:10
To: TurboGears
Subject: Re: [TurboGears] Setting up different auth Metadata providers for test/development/production