Version: 2.1.13 (Dublin, 4.0.0-ONAP)¶
Note: In general, Infrastructure must be accomplished in the release PRIOR to general usage. This is the case for most of the features included here.
- AAF has built the required features to automatically generate all Certificates and Configurations real-time. This will be utilized by ONAP MSs in El Alto
- AAF has the ability to publish both Public and Internal Private K8s Service information (Locator)
- Greatly Reduced size of Docker Images
- Greatly enhanced startup procedures in K8s, to more cleanly start, with Certificate, Property Generation every time
- Ability to run internally as non-root (fully setup K8s in El Alto)
- Removal of unused classes in Batch
- Large improvement in Batch and methodology, to be used in El Alto
- Bug Fixes
- AAF-797 Update IP address for aaf-onap-test.osaaf.org
- AAF-794 Misleading error message in agent.sh
- AAF-773 aaf-cass timing issues
- AAF-769 AAF CSIT not working
- AAF-727 Cert Subject Check confused by Email
- AAF-722 aaf continues to be available to aai-resources even though aaf database appears to be down
- AAF-720 Docker Images not passing Signal -1
- AAF-645 Fix “Null” string for fetching path inside CADI API enforcement filter
- AAF-522 rsa 4096 signing fails with TPM
- AAF-813 Missing Role for dmaap-bc Identity
- AAF-514 TPM Plugin: Remove global structure used for storing session data
- AAF-785 non STAGING version on master
- AAF-822 Startup issues with K8S, Certs
- Usage Notes
- AAF Core and SMS elements have consistently started from scratch. The one case where this didn’t happen for SMS,
- it was found that incompatible data was left in volume. Removal of old data for SMS (See SMS notes) should resolve
- On the same instance, one AAF Core component had a similar scenario. A simple bounce of aaf-locator resolved.
- Existing Cassandra
- For each release, AAF maintains the authz/auth/auth-cass/cass_init/init.cql which is used to setup Keyspaces from scratch
- Any changes are also done in small CQL files, you MIGHT need authz/auth/auth-cass/cass_init/init2_10.cql for Dublin
Version: 2.1.8 (Casablanca, 3.0.0-ONAP, Casablanca Maintenance Release)¶
Note: AAF did not create new artifacts for Casablanca Maintenance Release.
- 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.
- Bug Fixes
- AAF in OOM was not stable coming out of Beijing. AAF OOM was refactored using above Container based Configurations.
- AAF-617 LOCATE Proxy DELETE not working
- AAF-605 DB Stoppage not causing Reset of Connection
- AAF-601 Agent “showpass” errors on optional “chal” file, when not exists
- AAF-600 Bad Data for APPC in AAF Test Evironment
- AAF-598 Inconsistent Startup with truly persistent Cass Data
- AAF-597 Please change default email@example.com permission
- AAF-592 SDNC not able to authenticate with BAth username/password
- AAF-530 AAF inside Kubernetes inaccessible for clients from outside
- Known Issues
- REAL ONAP versus ONAP Test Environment - CA used in ONAP Test Environment should (of course) NOT be used by individual companies in REAL deployments. - Cassandra Instance in Kubernetes ONAP Test environment is a single instance. REAL deployments should follow global, multi-datacenter deployment strategies per Cassandra recommendations.
- AAF team organized all the Identities, all the Credentials, etc, on behalf of ONAP Apps.
- Security Notes
- AAF has achieved clean scans for everything in authz.git repo
- In the cadi.git (used for Adaptors), there is a Shiro adapter. Shiro itself has security flags, NOT the adapter, so understand the security issues of Shiro before use.
- AAF code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The AAF open Critical security vulnerabilities and their risk assessment have been documented as part of the project.
- Quick Links:
- Upgrade Notes
Version: 2.1.1 (Beijing, 2.0.0-ONAP)¶
- Service (primary) – All the Authorization information (more on that in a bit)
- Locate – how to find ANY OR ALL AAF instances across any geographic distribution
- OAuth 2.0 – new component providing Tokens and Introspection (no time to discuss here)
- GUI – Tool to view and manage Authorization Information, and create Credentials
- Certman – Certificate Manger, create and renew X509 with Fine-Grained Identity
- FS – File Server to provide access to distributable elements (like well known certs)
- Hello - Test your client access (certs, OAuth 2.0, etc)
- Bug Fixes
- Known Issues
- REAL ONAP versus ONAP Test Environment - Cassandra Instance in Kubernetes ONAP Test environment is a single instance. REAL deployments should follow global, multi-datacenter deployment strategies per Cassandra recommendations.
- Quick Links: