-
Epic
-
Resolution: Unresolved
-
High
-
None
-
None
-
Components may use HTTP as server and client
-
Non-Functional Requirement (DEPRECATED)
-
4
-
Not yet performed
-
De-Scoped
-
M
-
NO GO
-
Not used for this release
-
Not used for this release
Description of Use Case / Requirement:
As AAF is not a mandatory component and as TLS encryption may be done using service mesh, components must be able to server their traffic in plain HTTP and must be able to access other components using HTTP. Per default, HTTPS (client and server side) is mandated but configuration must allow HTTP.
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