HTTPS Proxy Configuration

1. OTT Packager Accessing to KSS services

The KSS services require AuthN token to authenticate request coming from OTT packagers pre-integrated with the CKS.

This article provides a proxy configuration example (based on NGINX@ widespread proxy server) forward OTT packager HTTP request to HTTPS SSP endpoint, that support pre-defined AuthN token (based on base64 JWT token standard) provided into "nv-authorizations" HTTP headers.

Please refer to (23.48) Authentication Management for more details on authentication token required by SSP SaaS.

NGINX server block config example to inject 'nv-authorizations' header (the AuthN token of the example is a test sample, you must replace it by the pre-defined one used during the CKS pre-integration):

CODE

server {

    listen 80;
    server_name backend.example.com

    location / {
        proxy_set_header nv-authorizations "eyJraWQiOiI0ODIxODIiLCJ0eXAiO ...";
        proxy_pass https://ssp.nagra.example.com;

        # To authenticate NGINX server on SSP upstream server
        # proxy_ssl_certificate     /etc/nginx/client.pem;
        # proxy_ssl_certificate_key /etc/nginx/client.key;

        # If self-signed certificate used
        # proxy_ssl_trusted_certificate /etc/nginx/trusted_ca_cert.crt;
        # proxy_ssl_verify       on;
        # proxy_ssl_verify_depth 2;

        # To reuse HTTPS session
        # proxy_ssl_session_reuse on;
    }
}