Release Notes:

Owned by Jonathan Gathman
Apr 10, 2018
1 min read

Beijing:

  AAF Beijing is instantiated in TEST Environment on April 9, 2018

  From a Code perspective, there are several important factors in Beijing that were not in Amsterdam

  1. AAF Components are ALL HTTP/S now

  2. Authentication by Client Certificate is supported and PREFFERED

  3. The SAME Certificate can be used for your Service Certificate, IF your clients are able to support the ONAP Root CA Certificate

  4. AAF Location Component allows you to find all instances running of AAF geographically

    1. DME2 is Removed, as AAF Location provides the ability to locate AAF Components globally.

  5. Access to AAF is direct HTTP/S

  6. OAuth2 is implemented