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
- AAF Components are ALL HTTP/S now
- Authentication by Client Certificate is supported and PREFFERED
- The SAME Certificate can be used for your Service Certificate, IF your clients are able to support the ONAP Root CA Certificate
- AAF Location Component allows you to find all instances running of AAF geographically
- DME2 is Removed, as AAF Location provides the ability to locate AAF Components globally.
- Access to AAF is direct HTTP/S
- OAuth2 is implemented