diff options
| author |   Jonathan Gathman <jonathan.gathman@att.com> | 2018-09-06 13:52:40 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2018-09-06 13:52:40 +0000 |
| commit | a398698b8c1c6975e6b25cfd019b26e930a110e3 (patch) | |
| tree | 517bee0ee138f4f76722e276afdf218a928da0c5 | |
| parent | 0f78ee6a1036271b46655d190f03edf6f7d0444b (diff) | |
| parent | 673fe81cf324ae42c64abbe33c07ee0215a0ef65 (diff) | |
Merge "Change : Spelling Issue Issue-ID: AAF-454"
| -rw-r--r-- | docs/sections/architecture/security.rst | 2 |
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. |