3 ms·
As for handling the TLS part, both Apache and NGINX have the capability to do verification of certificates. The application only needs to parse the headers they
by jeroenhd 7y ago
As for handling the TLS part, both Apache and NGINX have the capability to do verification of certificates. The application only needs to parse the headers they pass on to determine the user connecting to the application.
If you don't care about the user (TLS client certs + standard username/password) you can get away with proxying the application through nginx and calling it a day.
Basically you turn on client verification and you're done. If you want to show an error to unauthenticated users, you can make verification optional and add something along the lines of:
if ($ssl_client_verify != SUCCESS) {
return 403;
}