Its still the same command as described in the DefectDojo docs: kubectl port-forward --namespace=default \ service/defectdojo-django 8080:80.

I've you want to make local port-forwarding easier you can also add localhost to the list of allowed hosts in defectdojo: helm upgrade defectdojo ... --set="host=defectdojo-django.default.svc" --set="alternativeHosts[0]=localhost"

You should then be able to access defectdojo under localhost:8080

Hi,

I'm sorry for not getting back to you sooner.

We try connecting securecodebox and DefectDojo for weeks and change it to different websites (localhost, defectdojo-django.default.svc) and still didn't work. I also try your reply (helm upgrade defectdojo ... --set="host=defectdojo-django.default.svc") and still having problems.

This is the command that I input:

helm upgrade
defectdojo
./helm/defectdojo
--set django.ingress.enabled=${DJANGO_INGRESS_ENABLED}
--set django.ingress.activateTLS=${DJANGO_INGRESS_ACTIVATE_TLS}
--set createSecret=true
--set createRabbitMqSecret=true
--set createRedisSecret=true
--set createMysqlSecret=true
--set createPostgresqlSecret=true
--set="host=defectdojo-django.default.svc"
--set "alternativeHosts={localhost,defectdojo-django.default.svc}" -n

One problem that I think of is that the pods are not connecting because of EmptyDir (pod for the scan output and the other pod for defectdojo webhook). Can that be solved?

Its still the same command as described in the DefectDojo docs: kubectl port-forward --namespace=default \ service/defectdojo-django 8080:80.

I've you want to make local port-forwarding easier you can also add localhost to the list of allowed hosts in defectdojo: helm upgrade defectdojo ... --set="host=defectdojo-django.default.svc" --set="alternativeHosts[0]=localhost"

You should then be able to access defectdojo under localhost:8080

Hi J12934. I have a similar issue and have followed the above recommended fix but encountered a new error which i am not familiar and this is it

2022-03-16 04:16:42 INFO DefectDojoPersistenceProvider:24 - Starting DefectDojo persistence provider
2022-03-16 04:16:46 INFO DefectDojoPersistenceProvider:35 - Downloading Scan Result
2022-03-16 04:16:48 INFO DefectDojoPersistenceProvider:39 - Uploading Findings to DefectDojo at: http://defectdojo-django.default.svc
2022-03-16 04:16:48 INFO VersionedEngagementsStrategy:87 - Running with DefectDojo User Id: 42
2022-03-16 04:16:48 INFO VersionedEngagementsStrategy:194 - Using default ProductType as no 'defectdojo.securecodebox.io/product-type-name' annotation was found on the scan
Exception in thread "main" org.springframework.web.client.ResourceAccessException: I/O error on GET request for "http://defectdojo-django.default.svc/api/v2/products/": defectdojo-django.default.svc; nested exception is java.net.UnknownHostException: defectdojo-django.default.svc
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:785)
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:751)
at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:621)
at io.securecodebox.persistence.defectdojo.service.GenericDefectDojoService.internalSearch(GenericDefectDojoService.java:151)
at io.securecodebox.persistence.defectdojo.service.GenericDefectDojoService.search(GenericDefectDojoService.java:167)
at io.securecodebox.persistence.defectdojo.service.GenericDefectDojoService.searchUnique(GenericDefectDojoService.java:187)
at io.securecodebox.persistence.strategies.VersionedEngagementsStrategy.ensureProductExistsForScan(VersionedEngagementsStrategy.java:225)
at io.securecodebox.persistence.strategies.VersionedEngagementsStrategy.run(VersionedEngagementsStrategy.java:90)
at io.securecodebox.persistence.DefectDojoPersistenceProvider.main(DefectDojoPersistenceProvider.java:42)
Caused by: java.net.UnknownHostException: defectdojo-django.default.svc
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:229)
at java.base/java.net.Socket.connect(Socket.java:609)
at java.base/java.net.Socket.connect(Socket.java:558)
at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:182)
at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:474)
at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:569)
at java.base/sun.net.www.http.HttpClient.(HttpClient.java:242)
at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:341)
at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:362)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1253)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1187)
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1081)
at java.base/sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:1015)
at org.springframework.http.client.SimpleBufferingClientHttpRequest.executeInternal(SimpleBufferingClientHttpRequest.java:76)
at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48)
at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:66)
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:776)
... 8 more

These both still seem to be issues with the DefectDojo installation.
If the cluster internal domain names are making too much trouble, I'd recommend to set the defectDojo up to use a internal domain using a kubernetes ingress.

You can then make sure that this ingress is working correctly from your computer, once that up and runnign you can configure the secureCodeBox DefectDojo hook to use the same external url.

Noted, I will try this.