summaryrefslogtreecommitdiffstats
path: root/docs/sections/architecture/security.rst
diff options
context:
space:
mode:
authorankatare <ankatare@hotmail.com>2018-09-05 16:44:54 +0530
committerankatare <ankatare@hotmail.com>2018-09-05 16:44:54 +0530
commit673fe81cf324ae42c64abbe33c07ee0215a0ef65 (patch)
treefc325529a1eb52206b2d7b8768a7b16161189126 /docs/sections/architecture/security.rst
parent3819c03ec62382df78c7c62d93582398462c1974 (diff)
Change : Spelling Issue
Issue-ID: AAF-454 Change-Id: Ifee81d58e2559a78f4a79f3c82187ade16508921 Signed-off-by: ankatare <ankatare@hotmail.com>
Diffstat (limited to 'docs/sections/architecture/security.rst')
-rw-r--r--docs/sections/architecture/security.rst2
1 files changed, 1 insertions, 1 deletions
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.