-
Story
-
Resolution: Done
-
Medium
-
None
-
Policy 2022-08-31->2022-09-14, Policy 2022-09-14->2022-09-28, Policy 2022-09-28->2022-10-12, Policy 2022-10-12->2022-10-26
As a ONAP developer, I would like to support secured connections to the database for policy components, so data flows encrypted between policy components and the DB. This capability is even more important when the database resides outside the kubernetes cluster.
The work intended is to allow JDBC and other tooling such as mysql cli interface (if used by the component) additional flags to specify if the client connection to the database server should be secured, ie. "–ssl" flag in mysql or "useSSL=true" in JDCBC connections.
1.
|
Support secured DB communications for XACML-PDP | Closed | jhh | |
2.
|
Support secured DB communications for DB migrator | Closed | jhh | |
3.
|
OOM companion changes for secured DB communications | Closed | jhh | |
4.
|
Support secured DB communications for PAP | Closed | jhh | |
5.
|
Support secured DB communications for API | Closed | jhh | |
6.
|
Support secured DB communications for PDP-D APPS | Closed | jhh | |
7.
|
Support secured DB communications in APEX PDP | Closed | liamfallon |