On 20/4/17 3:16 pm, Chris Suttles wrote:
> https://bugs.launchpad.net/keystone/+bug/1662762
>
> I ran into this with an install of Ocata on ubuntu from packages (not using
> fuel). It sounds like you might be hitting this same issue. I was able to
> resolve it by grabbing core.py from the Ocata
https://bugs.launchpad.net/keystone/+bug/1662762
I ran into this with an install of Ocata on ubuntu from packages (not using
fuel). It sounds like you might be hitting this same issue. I was able to
resolve it by grabbing core.py from the Ocata version of the fix for this bug
and dropping it in
I should have said: This is on OpenStack Ocata, deployed with Fuel.
On 20/4/17 2:41 pm, Gregory Orange wrote:
> We have configured Keystone for LDAP authentication via the
> domain_specific_drivers_enabled setting and a file keystone..conf,
> and by tcpdump and LDAP server logs it appears to be
We have configured Keystone for LDAP authentication via the
domain_specific_drivers_enabled setting and a file keystone..conf, and
by tcpdump and LDAP server logs it appears to be working to some degree. That
is, if the wrong credentials are entered, the response says so. However with
the corre