This bug pointed out that some distros don't have the same pam Python
module packaged that this backend was expecting. In my case, on Fedora,
it's PAM and the API is not compatible with the pam module that was
used. This patch makes the backend support PyPAM, as well as the
original pam module that was used.
In order to test this, I updated the pam backend to the latest backend
API. Even though the base class will raise NotImplementedError, I
included all functions here to make it more clear all of the things
this backend does not do.
Reviewed: https:/ /review. openstack. org/5365 github. com/openstack/ keystone/ commit/ e67732748c7ad46 56f6ef5d9da3ff4 789199bf9a
Committed: http://
Submitter: Jenkins
Branch: master
commit e67732748c7ad46 56f6ef5d9da3ff4 789199bf9a
Author: Russell Bryant <email address hidden>
Date: Wed Mar 14 16:55:24 2012 -0400
Support PyPAM in pam backend, update to latest API
Fix bug 938801.
This bug pointed out that some distros don't have the same pam Python
module packaged that this backend was expecting. In my case, on Fedora,
it's PAM and the API is not compatible with the pam module that was
used. This patch makes the backend support PyPAM, as well as the
original pam module that was used.
In order to test this, I updated the pam backend to the latest backend rror, I
API. Even though the base class will raise NotImplementedE
included all functions here to make it more clear all of the things
this backend does not do.
Change-Id: I74144f4e63b683 0c8224bc87e1662 eb5df8728a0