| sg481n | faf7f2d | 2017-09-22 17:17:23 +0000 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | .. Copyright © 2017 AT&T Intellectual Property. All rights reserved. |
| 4 | |
| sg481n | a9d2108 | 2017-09-23 14:26:06 +0000 | [diff] [blame] | 5 | AAF - Application Authorization Framework |
| sg481n | faf7f2d | 2017-09-22 17:17:23 +0000 | [diff] [blame] | 6 | ================================================== |
| 7 | .. The purpose of AAF (Application Authorization Framework) is to organize software authorizations so that applications, tools and services can match the access needed to perform job functions. |
| 8 | |
| 9 | AAF is designed to cover Fine-Grained Authorization, meaning that the Authorizations provided are able to used an Application's detailed authorizations, such as whether a user may be on a particular page, or has access to a particular Pub-SUB topic controlled within the App. |
| 10 | |
| 11 | This is a critical function for Cloud environments, as Services need to be able to be installed and running in a very short time, and should not be encumbered with local configurations of Users, Permissions and Passwords. |
| 12 | |
| 13 | To be effective during a computer transaction, Security must not only be secure, but very fast. Given that each transaction must be checked and validated for Authorization and Authentication, it is critical that all elements on this path perform optimally. |
| 14 | |
| 15 | |
| Instrumental | bbe7154 | 2018-05-25 12:29:38 -0500 | [diff] [blame^] | 16 | Sections |
| 17 | ++++++++ |
| sg481n | faf7f2d | 2017-09-22 17:17:23 +0000 | [diff] [blame] | 18 | |
| 19 | .. toctree:: |
| Instrumental | bbe7154 | 2018-05-25 12:29:38 -0500 | [diff] [blame^] | 20 | :maxdepth: 2 |
| 21 | :glob: |
| 22 | |
| 23 | sections/* |
| Sai Gandham | d67a9de | 2018-05-25 15:48:11 +0000 | [diff] [blame] | 24 | |
| sg481n | faf7f2d | 2017-09-22 17:17:23 +0000 | [diff] [blame] | 25 | |
| 26 | Introduction |
| 27 | ------------ |
| 28 | AAF contains some elements of Role Based Authorization, but includes Attribute Based Authorization elements as well. |
| 29 | |
| sg481n | 2bc3538 | 2017-09-23 15:50:15 +0000 | [diff] [blame] | 30 | |image0| |
| 31 | |
| Instrumental | bbe7154 | 2018-05-25 12:29:38 -0500 | [diff] [blame^] | 32 | .. |image0| image:: images/aaf-object-model.jpg |
| sg481n | 2bc3538 | 2017-09-23 15:50:15 +0000 | [diff] [blame] | 33 | :height: 600px |
| 34 | :width: 800px |
| sg481n | faf7f2d | 2017-09-22 17:17:23 +0000 | [diff] [blame] | 35 | |
| 36 | |
| 37 | Essential Components |
| 38 | -------------------- |
| 39 | The core component to deliver this Enterprise Access is a RESTful service, with runtime instances registered in a Cloud Directory (DME2) and backed by a resilient Datastore (Cassandra as of release 1.3) |
| 40 | |
| 41 | The Data is managed by RESTful API, with Admin functions supplemented by Character Based User interface and certain GUI elements. |
| 42 | |
| 43 | -The Service accessible by provided Caching Clients and by specialized plugins |
| 44 | |
| 45 | -CADI (A Framework for providing Enterprise Class Authentication and Authorization with minimal configuration to Containers and Standalone Services) |
| 46 | |
| 47 | -Cassandra (GRID Core) |