You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have looked at the helm chart as well as the documentation to find out how I can secure the HTTP server of reposilite via TLS. Unfortunately without success, because there is explained How to configure the Javalin SSL plugin, but not how to start/configure reposilite with TLS certificates (HTTPS).
I would like to secure the communication between nginx ingress-controller and reposilite via TLS authentication and encryption.
If this is not possible with 3.x, that would be understandable. However, I would be very happy if this would be possible with the major release 4.x, especially since something about SSL build in is mentioned, it seems as if this will be taken care of. Nevertheless, I would like to draw attention to this missing feature.
Add an example how to deploy reposilite with TLS encryption
Option: Add a certificate resource (cert-manager), to automatically configure the helm chart for using the TLS certificates for TLS authentication / encryption.
The text was updated successfully, but these errors were encountered:
SSL sets up HTTPS for the http server (Jetty) we use internally. To be fair, we're not doing anything special on our side, so the approach is similar to other Java apps:
Request details
Hi,
I have looked at the helm chart as well as the documentation to find out how I can secure the HTTP server of reposilite via TLS. Unfortunately without success, because there is explained How to configure the Javalin SSL plugin, but not how to start/configure reposilite with TLS certificates (HTTPS).
I would like to secure the communication between nginx ingress-controller and reposilite via TLS authentication and encryption.
If this is not possible with 3.x, that would be understandable. However, I would be very happy if this would be possible with the major release 4.x, especially since something about SSL build in is mentioned, it seems as if this will be taken care of. Nevertheless, I would like to draw attention to this missing feature.
The text was updated successfully, but these errors were encountered: