AFAIK, you can't replace your authentication policy once your app has been initialized. If you need a different authentication policy for testing purposes, you may need to rethink how you are handling your test cases.
On Wed, Sep 23, 2015 at 8:50 AM, Achim Domma <[email protected]> wrote: > Hi, > > for testing purposes I want to replace my authentication policy. My app > has some setup(conf) method, which expects a Configurator and configures > the app. This method also configures the authentication and authorization. > In my test code, I set up a Configurator, pass it to my setup method and > want to replace the authorization afterwards. Calling > set_authentication_policy a second time seems not to have any effect. I > checked the source, but don't get exactly why?! Whether I call > conf.commit() before the second call or not, does not make a difference. > > Is there a way to replace an already configured authentication policy? > > cheers, > Achim > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" 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/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > -- Vincent Catalano Software Engineer and Web Developer, (520).603.8944 -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
