-
Bug
-
Resolution: Done
-
High
-
Frankfurt Release
-
None
According to read the docs there should be possibility to pre install root certificate for package validation by copping it directly to pod to /var/lib/jetty/cert in sdc-onboarding-be.
Currently when non root user has been introduced to sdc container it become impossible because cert folder is requires root privileges.
/var/lib/jetty $ ls -all total 140 drwxr-xr-x 1 jetty jetty 4096 Apr 22 14:42 . drwxr-xr-x 1 root root 4096 May 11 2019 .. -rw-rw-r-- 1 jetty jetty 65753 Apr 21 15:57 VSPPackage.zip drwxr-xr-x 2 root root 4096 Apr 22 13:15 cert drwxr-xr-x 1 jetty jetty 4096 Apr 21 13:34 chef-solo drwxr-xr-x 3 jetty jetty 4096 Apr 21 13:34 config drwxr-xr-x 2 jetty jetty 4096 Apr 21 13:34 etc -rw-r--r-- 1 jetty jetty 3579 Apr 21 13:34 jetty.start drwxr-xr-x 1 jetty jetty 4096 May 11 2019 lib drwxr-xr-x 2 jetty jetty 4096 Apr 22 00:00 logs -rwxr-xr-x 1 jetty jetty 289 Apr 21 13:34 ready-probe.sh drwxr-xr-x 1 jetty jetty 4096 May 11 2019 resources drwxr-xr-x 1 jetty jetty 4096 Apr 21 13:34 start.d -rwxrwx--- 1 jetty jetty 614 Apr 1 12:56 startup.sh drwxr-xr-x 2 jetty jetty 4096 Apr 21 13:34 temp -rw-r--r-- 1 jetty jetty 25 Apr 21 13:34 wait_logback.log drwxr-xr-x 1 jetty jetty 4096 Apr 1 13:07 webapps /var/lib/jetty $
In robot test cases we prepared test case that was loading cert directly to sdc onboarding pod and validating VSP both in VNFSDK and SDC. Now we cannot validate secured packages in sdc onboarading.