From 673fe81cf324ae42c64abbe33c07ee0215a0ef65 Mon Sep 17 00:00:00 2001 From: ankatare Date: Wed, 5 Sep 2018 16:44:54 +0530 Subject: Change : Spelling Issue Issue-ID: AAF-454 Change-Id: Ifee81d58e2559a78f4a79f3c82187ade16508921 Signed-off-by: ankatare --- docs/sections/architecture/security.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/sections/architecture/security.rst') diff --git a/docs/sections/architecture/security.rst b/docs/sections/architecture/security.rst index afc99295..d1809935 100644 --- a/docs/sections/architecture/security.rst +++ b/docs/sections/architecture/security.rst @@ -126,7 +126,7 @@ The AAF Suite provides the following elements: The Organization ---------------- -AAF is only a tool to reflect the Organization it is setup for. AAF does not, for instance, know what IDs are acceptable to a particular company. Every Organization (or Company) will also likely have its own Certificate Authority and DNS. Most importantly, each Organzation will have a hierarchy of who is responsible for any give person or application. +AAF is only a tool to reflect the Organization it is setup for. AAF does not, for instance, know what IDs are acceptable to a particular company. Every Organization (or Company) will also likely have its own Certificate Authority and DNS. Most importantly, each Organization will have a hierarchy of who is responsible for any give person or application. * AAF's Certman connects to the Organization's CA via SCEP protocol (Others can be created as well) * AAF ties into the Organizational hierarchy. Currently, this is through a feed of IDs and relationships. -- cgit 1.2.3-korg