Skip to content

Latest commit

 

History

History
126 lines (94 loc) · 3.83 KB

02-NGINX-Plus-Setup.md

File metadata and controls

126 lines (94 loc) · 3.83 KB
Raw

How To Set Up NGINX Plus OIDC for Ping Identity Integration

Take the following steps to set up NGINX Plus as the OpenID Connect relying party that runs.

Configure NGINX OpenID Connect

  1. Clone the nginx-openid-connect/nginx-oidc-ping-identity GitHub repository, or download the repo files.

    git clone https://github.com/nginx-openid-connect/nginx-oidc-ping-identity.git

  2. In the oidc_idp.conf, find the following directives($idp_domain, $oidc_client), and update them.

    You could find the IDP domain in the Basic Information section.

     map $x_client_id $idp_domain {
     # e.g., auth.pingone.us
     default "{{Edit-IdP-Domain}}";
 }

 map $x_client_id $idp_env_id {
     default "{{Edit-IdP-Environment-ID}}";
 }

 map $x_client_id $oidc_client {
     default "{{Edit-your-IdP-client-ID}}";
 }

  3. In the oidc_idp.conf, choose one of the following options.

    • Option 1. Update the following configuration if you don't enable PKCE.

      map $x_client_id $oidc_client_secret {
    default "{{Edit-Your-IDP-Client-Secret}}";
}

map $x_client_id $oidc_pkce_enable {
    default 0;
}

    • Option 2. Update the following configuration if you enable PKCE.

      map $x_client_id $oidc_client_secret {
    default ""; # Remove the client secret
}

map $x_client_id $oidc_pkce_enable {
    default 1;
}

  4. Optional: In the oidc_nginx_server.conf, update $resolver if you use local DNS servers.

     resolver   8.8.8.8;         # For global DNS lookup of IDP endpoint
          # xxx.xxx.xxx.xxx; # For your local DNS lookup
          # 127.0.0.11;      # For local Docker DNS lookup

Optional Configuration

This repo provides a sample container environment that contains the bundle frontend/backend applications. So you can skip this step if you would like to locally test using a container.

  1. In the oidc_frontend_backend.conf file, update the server IP addresses and ports under the upstreams of my_frontend_site and my_backend_app if you want to test your applications.

    # Sample upstream server for the frontend site.
#
upstream my_frontend_site {
    zone my_frontend_site 64k;
    server 127.0.0.1:9091;
}

# Sample upstream server for the backend app.
#
upstream my_backend_app {
    zone my_backend_app 64k;
    server 127.0.0.1:9092;
}

  2. Copy the following files to the /etc/nginx/conf.d directory on the host machine where NGINX Plus is installed if you want to test the files in your remote machine:

    • oidc_frontend_backend.conf
    • oidc.js
    • oidc_idp.conf
    • oidc_nginx_http.conf
    • oidc_nginx_server.conf
    • docker/build-context/nginx/test/proxy_server_test.conf

  3. Update /etc/nginx/nginx.conf with the following information if you want to test your applications in your remote machine:

     http {
         :
     include conf.d/oidc_idp.conf;
     include conf.d/oidc_nginx_http.conf;
     include conf.d/oidc_frontend_backend.conf;
     include test/proxy_server_test.conf;
         :
 }

  4. Copy the following directory to the /usr/share/nginx/html/ directory on the host machine where NGINX Plus is installed if you want to test the files in your remote machine:

     cp -R docker/build-context/content/ /usr/share/nginx/html/

    Note:

    Skip this step if you have your frontend files as these files are a sample frontend app to test the OIDC.

  5. Test and reload the NGINX configuration if you want to test the files in your remote machine:

    sudo nginx -t
sudo nginx -s reload