unable to load custom identity domain drivers

Bug #1803345 reported by Aleksei Kazaev
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Invalid
Undecided
Unassigned

Bug Description

What's the reason of disabling ability of using custom identity drivers in domain configs? The feature was removed in Pike release. As I understand, the only way to use them is copy source code to keystone.identity namespace. Could you suggest any other ways or workarounds for using custom specific code for identity drivers?
Example case - handle LDAP errors like password expiration in case of using ppolicy features in OpenLDAP (like password expire warning, login attempts warning, etc.)

Revision history for this message
Colleen Murphy (krinkle) wrote :

I don't believe we intentionally disabled the ability to use custom identity drivers. The instructions here should still work:

https://docs.openstack.org/keystone/latest/contributor/developing-drivers.html

You create your plugin with a setuptools entrypoint for keystone.identity. Can you explain what is not working? Or point to a release note or commit that removed the functionality you're looking for?

Changed in keystone:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Identity (keystone) because there has been no activity for 60 days.]

Changed in keystone:
status: Incomplete → Expired
Revision history for this message
Aleksei Kazaev (kazaev-alex) wrote :

Sorry for delay before answer. I used your suggestion (using a setuptools entrypoint). Of course, it works. Thanks a lot. The bug can be closed.

Changed in keystone:
status: Expired → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.