Fix MRI project list

[docs.git] / docs / developer-guide / authentication-and-authorization-services.rst

diff --git a/docs/developer-guide/authentication-and-authorization-services.rst b/docs/developer-guide/authentication-and-authorization-services.rst
index bb05ad86d0944df65189b64c740054335c1f7760..86772cc635763ced7094c3aeffce7eb2080778e2 100644 (file)
--- a/docs/developer-guide/authentication-and-authorization-services.rst
+++ b/docs/developer-guide/authentication-and-authorization-services.rst
@@ -353,7 +353,7 @@ which is hard-coded. The default domain can be also configured through the
 
 The protocol between the Controller and the Keystone Server (2) can be either
 HTTPS or HTTP. In order to use HTTPS the Keystone Server's certificate
-must be exported and imported on the Controller (see the :ref:`Certificate Management <Certificate Management>` section).
+must be exported and imported on the Controller (see the :ref:`Certificate Management <aaa-certificate-management>` section).
 
 Authorization Configuration
 ---------------------------
@@ -382,7 +382,7 @@ mechanism allows for a more robust configuration capabilities. `Shiro-based
 Authorization <http://shiro.apache.org/web.html#Web-%7B%7B%5Curls%5C%7D%7D>`_
 describes how to configure the Authentication feature in detail.
 
-.. notes::
+.. note::
 
     The Shiro-Based Authorization that uses the *shiro.ini* URLs section to
     define roles requirements is **deprecated** and **discouraged** since the
@@ -485,6 +485,8 @@ configuration, allowing different ways to listen for successful/unsuccessful
 authentication attempts. Custom AuthenticationListener(s) must implement
 the org.apache.shiro.authc.AuthenticationListener interface.
 
+.. _aaa-certificate-management:
+
 Certificate Management
 ----------------------