Description of Use Case / Requirement:

 AAF is not the only possible security solution for ONAP. In some cases ONAP may be deployed behind a reverse proxy or using service mesh. That's why components should be able to work (even in degradated mode in example using HTTP instead of HTTP or without authentication) without AAF available. The same for MSB. It's not the most cloud native solution for accessing services in kubernetes thus it should be possible to deploy ONAP without it and access services using for example API gateway.

Owners (one of these should be the Assignee - use @ notation): kopasiak sdesbure

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

Project Impact (Test Only (TO), Code (C)):

Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

Integration Leads (use @ notation): 

Company Engagement: Samsung, Orange