Skip to end of metadata
Go to start of metadata


Project NameApplication Authorization Framework
Target Release NameBeijing  Release
Project Lifecycle StateIncubation
Participating Company AT&T, Intel, Tech Mahindra


What is this release trying to address?

AAF trying to address the secured communication threw certificate management & token based Authentication,Authorization

Use Cases

The existing Amsterdam use cases are still going to be supported and additional use cases related to the will be supported for the Beijing Release

Minimum Viable Product

For Beijing release, the minimum viable product we are targeting is  integrating AAF  with multiple ONAP applications and perform secured transactions.


List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.


Key Summary T Created Updated Due Assignee Reporter P Status Resolution


Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Longer term roadmap

 AAF is to organize software authorizations so that applications, tools and services can match the access needed to perform job functions.  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.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.

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name

Deliverable Description

AAF integration with Appc

AAF Git repository
AAF source codeAAF Git repository
AAF libraryONAP Nexus repository
AAF API descriptionONAP wiki
AAF Release NotesONAP wiki
AAF DocumentationAAF Git repository


As part of the Beijing release,Certificate Management will be added to the AAF



High level architecture diagram

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01Run performance basic test, depends on performance criteria availability for level 1
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01Participate to Stability runs Level 1
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01Reach CII passing badge, increasing test coverage as remaining item
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability01Reach Level 1 single site horizontal scaling
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11Using LOG4J common framework for logging
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11API documentation provided
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

    • API Incoming Dependencies

  • List the API this project is expecting from other projects.
    Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

    Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

    API Name

    API Description

    API Definition Date

    API Delivery date

    API Definition link (i.e.swagger)


    • API Outgoing Dependencies

    API this project is delivering to other projects.

    API Name

    API Description

    API Definition Date

    API Delivery date

    API Definition link (i.e.swagger)

    ProvisiningAPI for creating,deleting and listing the administrative objectsAug 02 2017March 08 2018AAF API
    Admin APIAPI for the admin accessAug 02 2017March 08 2018AAF API

    Third Party Products Dependencies

    Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
    List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).




    DockerContainer engine1.12
    Cassandradatabase container2.1.16

    In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

    Testing and Integration Plans

    Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

    Describe the plan to integrate and test the release deliverables within the overall ONAP system.
    Confirm that resources have been allocated to perform such activities.

    AAF will invest in CSIT tests to allow further integration testing, AAF already provided some tests as part of R1.


    This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
    List identified release gaps (if any), and its impact.

    Gaps identified


    Testing/Integrationlimited testing of final product
  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  • Risks

    No known risks so far.


Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

  • Team Internal Milestone

  • This section may be used to document internal milestones that the team agreed on.

    Also, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, provide these agreements and dates in this section.

    It is not expected to have a detailed project plan.




    To fill outAAFAAF - CertMan,oAuth

    Documentation, Training


The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

Other Information

  • Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.

  • Free and Open Source Software

FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.

  • No labels