Skip to content

Commit

Permalink
added LDAP section to architecture and architecture
Browse files Browse the repository at this point in the history
https://bugs.launchpad.net/keystone/+bug/949521

Bug 949521

Change-Id: I2e37c0d946e3d97a2c4bc4bf4a50bd94466f70c2
  • Loading branch information
Adam Young committed Mar 13, 2012
1 parent e65a22c commit 5b3e05b
Show file tree
Hide file tree
Showing 2 changed files with 45 additions and 3 deletions.
6 changes: 6 additions & 0 deletions doc/source/architecture.rst
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,12 @@ interpolation)::
catalog.RegionOne.identity.internalURL = http://localhost:$(public_port)s/v2.0
catalog.RegionOne.identity.name = 'Identity Service'


LDAP Backend
-----------------
The LDAP backend stored Users and Tenents in separate Subtrees. Roles are recorded
as entries under the Tenants.

----------
Data Model
----------
Expand Down
42 changes: 39 additions & 3 deletions doc/source/configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
not use this file except in compliance with the License. You may obtain
a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0
http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
Expand Down Expand Up @@ -516,7 +516,7 @@ exmaple::

keyword arguments

* user <user-id>
* user <user-id>
* role <role-id>
* tenant_id <tenant-id>

Expand All @@ -532,7 +532,7 @@ example::

keyword arguments

* user <user-id>
* user <user-id>
* role <role-id>
* tenant_id <tenant-id>

Expand Down Expand Up @@ -595,3 +595,39 @@ example::

$ keystone service-delete 08741d8ed88242ca88d1f61484a0fe3b


Configuring the LDAP Identity Provider
===========================================================

As an alternative to the SQL Databse backing store, Keystone can Use a
Directory server to provide the Identity service. An example Schema
for openstack would look like this::

dn: cn=openstack,cn=org
dc: openstack
objectClass: dcObject
objectClass: organizationalUnit
ou: openstack

dn: ou=Groups,cn=openstack,cn=org
objectClass: top
objectClass: organizationalUnit
ou: groups

dn: ou=Users,cn=openstack,cn=org
objectClass: top
objectClass: organizationalUnit
ou: users

dn: ou=Roles,cn=openstack,cn=org
objectClass: top
objectClass: organizationalUnit
ou: users

The corresponding entries in the Keystone configuration file are::

[ldap]
url = ldap://localhost
suffix = dc=openstack,dc=org
user = dc=Manager,dc=openstack,dc=org
password = badpassword

0 comments on commit 5b3e05b

Please sign in to comment.