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
While using nsi-safnari as part of a nsi-node deployment together with nsi-opennsa and nsi-envoy, it turned out that the HTTP client used in nsi-safnari is not sending a Server Name Indication (SNI) while trying to access nsi-opennsa via nsi-envoy. This was confirmed by examining the nsi-envoy debug logs.
Upgrading this project to a bit more recent version of its dependencies will most likely solve this problem since SNI support is common to almost all recent libraries and frameworks.
- allow all hosts with play.filters.hosts
- configure application secret with play.http.secret.key
- configure key- and truststore with play.ws.ssl
- fix issue #21 HTTP client does not do SNI
- simpler Dockerfile uses release zip from GitHub
- re-added sbt-less to create main.css
Description
While using nsi-safnari as part of a nsi-node deployment together with nsi-opennsa and nsi-envoy, it turned out that the HTTP client used in nsi-safnari is not sending a Server Name Indication (SNI) while trying to access nsi-opennsa via nsi-envoy. This was confirmed by examining the nsi-envoy debug logs.
Upgrading this project to a bit more recent version of its dependencies will most likely solve this problem since SNI support is common to almost all recent libraries and frameworks.
Tasks
The text was updated successfully, but these errors were encountered: