[DMAAP-DR] Doc updates for AAF and tlsEnabled

[dmaap/datarouter.git] / docs / architecture.rst

diff --git a/docs/architecture.rst b/docs/architecture.rst
index 6f29e5d..7310573 100644 (file)
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -1,5 +1,6 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
+.. _architecture:
 
 Architecture
 ============
@@ -9,13 +10,6 @@ Capabilities
 The DMaaP Data Router (DR) provisioning API is an HTTPS-based, REST-like API for creating and managing
 DR feeds and subscriptions, which provides a pub/sub architectural model for the transfer of data.
 
-The DR API also supports `AAF CADI authorization <https://docs.onap.org/en/latest/submodules/aaf/authz.git/docs/sections/architecture/cadi.html#authorization>`_.
-
-To use this feature, the API client must provide a valid AAF AppID / MechID with each request.
-To enable this feature, see the :ref:`configuration` section.
-
-.. note:: In future releases, AAF CADI auth will be enabled by default.
-
 Usage Scenarios
 ---------------
 Typically, DR pub clients request the provisioning of a new DR feed.
@@ -53,4 +47,4 @@ DMaaP DR architecture uses the Eclipse Jetty server as an application server to
 
 DMaaP DR uses MariaDB as it's storage component for the following:
    * DR Provisioning data. (feeds, subscribers, etc.)
-   * Historical logging data related to feed activity. (Publish, Delivery, etc.)
\ No newline at end of file
+   * Historical logging data related to feed activity. (Publish, Delivery, etc.)