Merge "Rename admin-guide files: keystone -> identity"
This commit is contained in:
@@ -7,8 +7,8 @@ Integrate Identity with LDAP
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
keystone-integrate-identity-backend-ldap.rst
|
||||
keystone-secure-identity-to-ldap-backend.rst
|
||||
identity-integrate-identity-backend-ldap.rst
|
||||
identity-secure-identity-to-ldap-backend.rst
|
||||
|
||||
The OpenStack Identity service supports integration with existing LDAP
|
||||
directories for authentication and authorization services. LDAP back
|
||||
@@ -15,15 +15,15 @@ command-line client.
|
||||
:maxdepth: 1
|
||||
|
||||
identity-concepts.rst
|
||||
keystone-certificates-for-pki.rst
|
||||
keystone-domain-specific-config.rst
|
||||
keystone-external-authentication.rst
|
||||
keystone-integrate-with-ldap.rst
|
||||
keystone-tokens.rst
|
||||
keystone-token-binding.rst
|
||||
keystone-fernet-token-faq.rst
|
||||
keystone-use-trusts.rst
|
||||
keystone-caching-layer.rst
|
||||
identity-certificates-for-pki.rst
|
||||
identity-domain-specific-config.rst
|
||||
identity-external-authentication.rst
|
||||
identity-integrate-with-ldap.rst
|
||||
identity-tokens.rst
|
||||
identity-token-binding.rst
|
||||
identity-fernet-token-faq.rst
|
||||
identity-use-trusts.rst
|
||||
identity-caching-layer.rst
|
||||
identity-keystone-usage-and-features.rst
|
||||
identity-auth-token-middleware.rst
|
||||
identity-service-api-protection.rst
|
||||
|
||||
@@ -88,7 +88,7 @@ information stored in the token and integrity is verified with a ``SHA256
|
||||
HMAC`` signature. Only the Identity service should have access to the keys used
|
||||
to encrypt and decrypt fernet tokens. Like UUID tokens, fernet tokens must be
|
||||
passed back to the Identity service in order to validate them. For more
|
||||
information on the fernet token type, see the :doc:`keystone-fernet-token-faq`.
|
||||
information on the fernet token type, see the :doc:`identity-fernet-token-faq`.
|
||||
|
||||
PKI and PKIZ tokens
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
@@ -101,4 +101,4 @@ pairs and certificates in order to create and validate PKI tokens.
|
||||
The same concepts from PKI tokens apply to PKIZ tokens. The only difference
|
||||
between the two is PKIZ tokens are compressed to help mitigate the size issues
|
||||
of PKI. For more information on the certificate setup for PKI and PKIZ tokens,
|
||||
see the :doc:`keystone-certificates-for-pki`.
|
||||
see the :doc:`identity-certificates-for-pki`.
|
||||
Reference in New Issue
Block a user