[PATCH] Using your own identity provider without modifying turbogears files

this is something that needs some work sadly it will be for the 1.1 release since 1.0 is feature freeze.

Currently the support for custom providers is a bit rough as you found out I like your idea, could you provide a patch for it?

if you ad yourself to the CC field it should email you.

Workaround: Use load_class to treat config option as a class path

Here's a little workaround for this issue. The patch modifies the create_default_provider function in turbogears/identity/__init__.py to be a little more flexible. First it searches for the requested identity provider plugin as usual, if it can't be found, it assumes that the identity.provider option is a class path and tries to resolve the class with the load_class function.

custom_identity_provider.diff

Replying to lilian:

We needed to use our own identity provider and to do that we had to modify entry_points.txt and we had to add our plugin provider module under turbogears/identity. Modifying any of the files in the directory where turbogears was installed is a problem for us

See http://parakeetprintquota.org/svn/tags/0.1.0/setup.py for a real-world example of a third-party identity provider being used without any modification of Turbogears itself - this is the whole point of entry points :-)

Batch moved into unclassified from 1.1 to properly track progress on the later

Amend subject so we know there is a proposed patch in there ...

It is not really needed because you just need to declare an entrypoint in your own application's setup.py file like this:

entry_points = """

[turbogears.identity.provider] customsaprovider= myapp.customsaprovider:CustomSqlAlchemyIdentityProvider """,

and then just use

identity.provider = customsaprovider

in your app.cfg file...

But this makes things a little easier to have this mechanism anyway :)

applied. Thanks aalbrecht.