+ - AAF created a local CA and CA Strategy to be utilized for ONAP Test Environments that can instantiated daily, yet have continuity over time and environments. (REAL ONAP instantiations should use their *own* CAs outside of initial tests.)
+ - AAF has auto-creation of configurations and certificates. This is expected to be done inside an "agent" container, and used by Apps.
+ - AAF stores and creates "Bootstrap Data" for all users of AAF in ONAP. This simplifies the efforts of ONAP components to organize their Authorizations, and so that various Test Environments can start with correct data every time.
+ - Refactored all of AAF instantiations to use the above, and have consistency between the 5 ways to start AAF.
+ - Ability for CADI Clients to map previous User/Password combinations to current credentials for migration purposes. This is applied to Shiro Plugin as well
+ - CADI Coarse Grain Enforcement Point (Authorize API access).
+ - Created Backward compatibility features, both for DB (Cassandra) and for API access.
+