You are correct. It wasn't updated to 2.4 I'll update that page as soon as I can.
You can use the plugins if you want. That's not going to be removed. What changed is just that in most simple cases, instead of having to write a whole repoze plugin, you can just edit the `authenticate` method in ApplicationAuthMetadata and authenticate the user there. To authenticate against a sqlalchemy/mongodb dataset the default quickstart now goes that way so it's easier for turbogears users to tweak the authentication as they wish. So generally the repoze.who plugins for sqlalchemy and mongo are now pointless (and are no longer needed nor installed by the quickstart). But other kind of plugins, like the LDAP one, are still perfectly available and usable. On Thu, Sep 26, 2019 at 11:32 AM Enrico Secco <enricosecco0...@gmail.com> wrote: > Hi Alessandro, > Thanks for the reply. > I tried to implement the proposed solution in the documentation: > https://turbogears.readthedocs.io/en/latest/cookbook/ldap-auth.html > The page appears to be outdated. I thought it was up to date because the > example uses the new approach: > > from tg.configuration.auth import TGAuthMetadata > class ApplicationAuthMetadata (TGAuthMetadata): > > > But he doesn't use blueprints > . Is it a mix of old and new style? > > But then, if I can't use repoze.who plugins, do I have to import a generic > LDAP connection package and write my functions? > > Best regards. > Enrico > > Il giorno mercoledì 25 settembre 2019 22:03:18 UTC+2, Alessandro Molina ha > scritto: >> >> Hi Enrico, >> >> Newer versions of TG don't use the sqlalchemy plugin of repoze anymore, >> that was replace by the authenticate method in ApplicationAuthMetadata. >> See >> https://turbogears.readthedocs.io/en/latest/turbogears/authentication.html?highlight=authenticate#authenticating-user >> and >> https://turbogears.readthedocs.io/en/latest/turbogears/authentication.html?highlight=authenticate#customizing-the-model-structure-assumed-by-the-quickstart >> for >> a small example. So you should be able to add an "authenticate" method >> to ApplicationAuthMetadata and get rid of repoze.who.plugins.sa >> >> Regarding ApplicationAuthMetadata itself, you want to initialise it with >> the specific arguments it needs instead of passing the whole `sa_auth` >> object. You can of course pass base_config.get_blueprint_view("sa_auth") to >> do exactly what you were doing before, but I'd say it's just best to pass >> the explicit things that you want in __init__ >> >> >> >> On Wed, Sep 18, 2019 at 2:30 PM Enrico Secco <enricos...@gmail.com> >> wrote: >> >>> Hi, I'm trying to implement a connection to the active directory system >>> of my domain. >>> In the documentation I find the necessary change to the app_cgf.py file. >>> But it seems to me related to the old versions because it uses: >>> base_config.auth_backend = 'ldapauth' >>> without using the new method: base_config.update_blueprint >>> I tried to translate the code for 2.4, assuming I could transform (I >>> don't know if it is correct ...): >>> base_config.sa_auth.cookie_secret = 'secret' >>> base_config.auth_backend = 'ldapauth' >>> >>> in: >>> base_config.update_blueprint ({ >>> 'sa_auth.cookie_secret': 'secret', >>> 'auth_backend': 'ldapauth', >>> }) >>> >>> >>> But when I go to define: >>> class ApplicationAuthMetadata (TGAuthMetadata): >>> def __init __ (self, sa_auth): >>> self.sa_auth = sa_auth >>> >>> to then connect it to the configuration: >>> base_config.sa_auth.authmetadata = ApplicationAuthMetadata ( >>> base_config.sa_auth) >>> >>> >>> with the update_blueprint method I cannot pass the sa_auth parameter >>> which is not defined. >>> >>> base_config.update_blueprint ({ >>> 'sa_auth.authmetadata': ApplicationAuthMetadata (?????????????) >>> }) >>> >>> >>> I get the impression that there are also repoze.who problems because I >>> had to modify repoze.who.plugins.sa (implements -> @implementer). So >>> maybe python3 porting is not yet possible ... >>> >>> Any advice is appreciated. >>> Thanks in advance. >>> Enrico >>> >>> -- >>> 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 turbo...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/turbogears/cbe07668-6710-4ebc-8a30-6cd676161bcc%40googlegroups.com >>> <https://groups.google.com/d/msgid/turbogears/cbe07668-6710-4ebc-8a30-6cd676161bcc%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/turbogears/4248a697-daf2-4e96-b97e-4f61ab0dceca%40googlegroups.com > <https://groups.google.com/d/msgid/turbogears/4248a697-daf2-4e96-b97e-4f61ab0dceca%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/turbogears/CAJfq2JHh%2B5zzN1sXh3r_sM-5%3DxQ8%3DL9dJgJZQ1sNAb767yoe%2BA%40mail.gmail.com.
