Hey all,
I have some questions about using the LDAP backend for keystone.
I'm in what seems to be an odd situation. I have an organization-wide
DLAP directory that already exists. All of our users will have access
to OpenStack, so we want to tie directly into this directory. However,
3, 2013 at 12:05 PM, Steven Presser spres...@jhu.edu
mailto:spres...@jhu.edu wrote:
Hey all,
I have some questions about using the LDAP backend for
keystone. I'm in what seems to be an odd situation. I have an
organization-wide DLAP directory that already exists. All of our
yet?
On 03/04/2013 04:08 PM, Steven Presser wrote:
This is what came out of my logs. I've bolded what looks relevant to me:
LDAP init: url=ldap://typhon.acm.jhu.edu
2013-03-04 16:06:01DEBUG [keystone.common.ldap.core] LDAP bind:
dn=cn=admin,ou=OpenStack,dc=acm,dc=jhu,dc=edu
2013-03-04 16:06
, Dolph Mathews wrote:
Yes, this feature just landed during grizzly-m3.
Which docs are you referring to? The variable wasn't included in
folsom's etc/keystone.conf.sample, for example.
-Dolph
On Mon, Mar 4, 2013 at 3:35 PM, Steven Presser spres...@jhu.edu
mailto:spres...@jhu.edu wrote
/master/
http://docs.openstack.org/master/ to match expectations, would that
have helped in your case? Thanks for clarifying.
Anne
On Mon, Mar 4, 2013 at 4:22 PM, Steven Presser spres...@jhu.edu
mailto:spres...@jhu.edu wrote:
Apparently the trunk docs. I could have sworn that wasn't what
5 matches
Mail list logo
