diff --git a/doc/admin-guide-cloud-rst/source/identity_auth_token_middleware.rst b/doc/admin-guide-cloud-rst/source/identity_auth_token_middleware.rst
index dbeb99223e..72fffa4ce8 100644
--- a/doc/admin-guide-cloud-rst/source/identity_auth_token_middleware.rst
+++ b/doc/admin-guide-cloud-rst/source/identity_auth_token_middleware.rst
@@ -20,12 +20,6 @@ Compute, for example, you can remove the middleware parameters from
     [filter:authtoken]
     paste.filter_factory = keystonemiddleware.auth_token:filter_factory
 
-.. note::
-
-    Prior to the Juno release, ``the auth_token`` middleware was in
-    ``python-keystoneclient``. The ``filter_factory`` must be set to
-    ``keystoneclient.middleware.auth_token:filter_factory`` in those
-    releases.
 
 And set the following values in :file:`nova.conf` as follows:
 
@@ -78,9 +72,3 @@ This sample paste config filter makes use of the :code:`admin_user` and
     ``auth_protocol`` options because the ``identity_uri`` option
     replaces them.
 
-.. note::
-
-    Prior to the Juno release, the ``auth_token middleware`` was in
-    ``python-keystoneclient``. The ``filter_factory`` must be set to
-    ``keystoneclient.middleware.auth_token:filter_factory`` in those
-    releases.
diff --git a/doc/admin-guide-cloud-rst/source/identity_troubleshoot.rst b/doc/admin-guide-cloud-rst/source/identity_troubleshoot.rst
index a0aeec95a7..69702628ab 100644
--- a/doc/admin-guide-cloud-rst/source/identity_troubleshoot.rst
+++ b/doc/admin-guide-cloud-rst/source/identity_troubleshoot.rst
@@ -40,14 +40,6 @@ section like this:
     admin_tenant_name = service
     admin_user = glance
 
-If your service lacks this stanza, the
-`keystoneclient/middleware/auth\_token.py <https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198>`__
-file specifies the defaults. If no value is specified for this directory, it `defaults to a secure temporary directory. <https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299>`__
-Initialization code for the service checks that the directory exists and
-is writable. If it does not exist, the code tries to create it. If this
-fails, the service fails to start. However, it often succeeds but
-problems occur later.
-
 The first thing to check is that the ``signing_dir`` does, in fact,
 exist. If it does, check for certificate files:
 
diff --git a/doc/admin-guide-cloud/ch_identity_mgmt.xml b/doc/admin-guide-cloud/ch_identity_mgmt.xml
index 8435e27c9e..6c4e4f9664 100644
--- a/doc/admin-guide-cloud/ch_identity_mgmt.xml
+++ b/doc/admin-guide-cloud/ch_identity_mgmt.xml
@@ -119,16 +119,7 @@ openstack --os-username admin --os-password secrete --os-project-name admin proj
     <para>For services that have a separate paste-deploy .ini file,
       you can configure the authentication middleware in the
         <literal>[keystone_authtoken]</literal> section of the main
-      configuration file, such as <filename>nova.conf</filename>. In
-      Compute, for example, you can remove the middleware parameters
-      from <filename>api-paste.ini</filename>, as follows:</para>
-    <programlisting language="ini"><?db-font-size 75%?>[filter:authtoken]
-paste.filter_factory = keystonemiddleware.auth_token:filter_factory</programlisting>
-    <note><para>Prior to the Juno release, the auth_token middleware was in
-        python-keystoneclient. The filter_factory must be set to
-        <literal>keystoneclient.middleware.auth_token:filter_factory</literal>
-        in those releases.
-    </para></note>
+      configuration file, such as <filename>nova.conf</filename>.</para>
     <para>And set the following values in
         <filename>nova.conf</filename> as follows:</para>
     <programlisting language="ini"><?db-font-size 75%?>[DEFAULT]
@@ -173,11 +164,6 @@ admin_password = keystone123</programlisting>
         <literal>auth_protocol</literal> options because the
         <literal>identity_uri</literal> option replaces them.</para>
     </note>
-    <note><para>Prior to the Juno release, the auth_token middleware was in
-        python-keystoneclient. The filter_factory must be set to
-        <literal>keystoneclient.middleware.auth_token:filter_factory</literal>
-        in those releases.
-    </para></note>
   </section>
    <section xml:id="identity-service-api-protection-with-role-based-access-control">
       <title>Identity API protection with role-based access control (RBAC)
diff --git a/doc/common/section_identity-troubleshooting.xml b/doc/common/section_identity-troubleshooting.xml
index eb3e5e7cff..042db7aafe 100644
--- a/doc/common/section_identity-troubleshooting.xml
+++ b/doc/common/section_identity-troubleshooting.xml
@@ -37,18 +37,6 @@ auth_uri = http://<replaceable>controller</replaceable>:5000/v2.0
 identity_uri = http://<replaceable>controller</replaceable>:35357
 admin_tenant_name = service
 admin_user = glance</programlisting>
-        <para>If your service lacks this stanza, the <link
-                xlink:href="https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L198"
-                >keystoneclient/middleware/auth_token.py</link> file
-            specifies the defaults. If no value is specified for this
-            directory, it <link
-                xlink:href="https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L299"
-                >defaults to a secure temporary directory.</link>
-            Initialization code for the service checks that the
-            directory exists and is writable. If it does not exist,
-            the code tries to create it. If this fails, the service
-            fails to start. However, it often succeeds but problems
-            occur later.</para>
         <para>The first thing to check is that the
                 <literal>signing_dir</literal> does, in fact, exist.
             If it does, check for the presence of the certificate