openstack
/
keystone-specs
Code Issues Proposed changes

Fix spelling in explicit domain id specification 

Change-Id: I67bd84f69208348e7a7e8719d6e6f1acd00bf9db
This commit is contained in:
Lance Bragstad 2018-10-23 09:20:23 +00:00
parent c54a16fd19
commit 92262db93c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/keystone/stein/explicit-domains-ids.rst
View File

@ -29,7 +29,7 @@ different Keystone servers.
To avoid this, operators want to keep the LDAP users in a domain with To avoid this, operators want to keep the LDAP users in a domain with
a consistent ID across deployments. The only domain with a a consistent ID across deployments. The only domain with a
predictable ID, however, is `default.` Tee default domain is used predictable ID, however, is `default.` The default domain is used
during the initial install, and thus has service users. Thus, it is during the initial install, and thus has service users. Thus, it is
impractical to put the LDAP users in the default domain. If a site impractical to put the LDAP users in the default domain. If a site
wished to have two LDAP servers in domain specific backends, only one wished to have two LDAP servers in domain specific backends, only one