I suppose you should be able to do that on after_init_config changing conf accordingly at least on 2.3.8 but I actually didn't try it
On Wed, Apr 13, 2016 at 5:00 PM, Luke Tunmer <[email protected]> wrote: > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
