[DMAAP-DR] Update oparent to 3.3.3

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

diff --git a/docs/architecture.rst b/docs/architecture.rst
index cae6bca..e3acc46 100644 (file)
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -10,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.
@@ -36,9 +29,9 @@ the DR provisioning API to manage feeds and subscriptions.
 
 See DMaaP Bus Controller API docs for more information:
 
-`Bus Controller Feeds API <https://onap.readthedocs.io/en/latest/submodules/dmaap/dbcapi.git/docs/api.html#feeds>`_
+`Bus Controller Feeds API <https://docs.onap.org/projects/onap-dmaap-buscontroller/en/latest/apis/api.html#feeds>`_
 
-`Bus Controller Subs API <https://onap.readthedocs.io/en/latest/submodules/dmaap/dbcapi.git/docs/api.html#dr-subs>`_
+`Bus Controller Subs API <https://docs.onap.org/projects/onap-dmaap-buscontroller/en/latest/apis/api.html#dr-subs>`_
 
 
 High level Architecture