|
| 1 | +# -----------------------------------------------------------------------------# |
| 2 | +# # |
| 3 | +# Sample Reverse Proxy Configuration: Frontend Site, Backend App # |
| 4 | +# (for Open ID Connect workflow) # |
| 5 | +# # |
| 6 | +# -----------------------------------------------------------------------------# |
| 7 | + |
| 8 | +# -----------------------------------------------------------------------------# |
| 9 | +# # |
| 10 | +# 1. Basic Example: Landing page starts OIDC workflow w/o login/logout button. # |
| 11 | +# # |
| 12 | +# -----------------------------------------------------------------------------# |
| 13 | + |
1 | 14 | # This is the backend application we are protecting with OpenID Connect |
2 | 15 | upstream my_backend { |
3 | 16 | zone my_backend 64k; |
@@ -33,4 +46,104 @@ server { |
33 | 46 | } |
34 | 47 | } |
35 | 48 |
|
| 49 | +# -----------------------------------------------------------------------------# |
| 50 | +# # |
| 51 | +# 2. Advanced Example: Landing page, login/logout button to handle OIDC kflow # |
| 52 | +# # |
| 53 | +# - Landing page shows 'login' button # |
| 54 | +# - 'login' button calls `/login` endpoint to start OIDC flow by validating |
| 55 | +# 'id_token' w/ IdP's JWK. # |
| 56 | +# - Landing page calls `/userinfo` to show user info using 'access_token`. # |
| 57 | +# - 'logout' button to be finished OIDC session by IdP. # |
| 58 | +# - API authorization by validating `access_token` w/ IdP's JWK # |
| 59 | +# # |
| 60 | +# -----------------------------------------------------------------------------# |
| 61 | + |
| 62 | +# |
| 63 | +# Upstream server for proxing to the frontend site. |
| 64 | +# - This is a bundle frontend app to locally test NGINX Plus OIDC workflow. |
| 65 | +# + Sample: ./docker/build-context/nginx/sample/proxy_server_frontend.conf |
| 66 | +# - Modify this configuration to match your frontend site. |
| 67 | +# |
| 68 | +upstream my_frontend_site { |
| 69 | + zone my_frontend_site 64k; |
| 70 | + server 127.0.0.1:9091; |
| 71 | +} |
| 72 | + |
| 73 | +# |
| 74 | +# Upstream sample for proxing to the backend API server. |
| 75 | +# - This is a bundle backend app to locally test an API using access token. |
| 76 | +# + Sample: ./docker/build-context/nginx/sample/proxy_server_backend.conf |
| 77 | +# - Modify this configuration to match your backend app. |
| 78 | +# |
| 79 | +upstream my_backend_app { |
| 80 | + zone my_backend_app 64k; |
| 81 | + server 127.0.0.1:9092; |
| 82 | +} |
| 83 | + |
| 84 | +# |
| 85 | +# Sample Frontend-site & backend-api-server for the OIDC workflow. |
| 86 | +# |
| 87 | +server { |
| 88 | + # Enable when debugging is needed. |
| 89 | + error_log /var/log/nginx/error.log debug; # Reduce severity level as required |
| 90 | + access_log /var/log/nginx/access.log main; |
| 91 | + |
| 92 | + # Replace the following server name with your host name. |
| 93 | + # |
| 94 | + # [Example: if you want to locally test OIDC in your laptop] |
| 95 | + # - Add '127.0.0.1 nginx.oidc.test` in your `/etc/hosts'. |
| 96 | + # - Use the command like 'make start'. |
| 97 | + # - Type 'https://nginx.oidc.test' in your browser. |
| 98 | + # - You will see the sample landing page and 'Sign In' button. |
| 99 | + # |
| 100 | + listen 8020; # Use SSL/TLS in production |
| 101 | + server_name nginx.oidc.test; |
| 102 | + |
| 103 | + # Replace the following files with your certificate. |
| 104 | + ssl_certificate /etc/ssl/nginx/nginx-repo.crt; |
| 105 | + ssl_certificate_key /etc/ssl/nginx/nginx-repo.key; |
| 106 | + |
| 107 | + # OIDC workflow |
| 108 | + include conf.d/openid_connect.server_conf; |
| 109 | + |
| 110 | + # |
| 111 | + # Frontend example: |
| 112 | + # |
| 113 | + # - Default landing page: no need OIDC workflow to show 'Sign In' button. |
| 114 | + # - The site is protected with OpenID Connect(OIDC) by calling the API |
| 115 | + # endpoint of `/login` when users click 'login' button. |
| 116 | + # |
| 117 | + location / { |
| 118 | + proxy_pass http://my_frontend_site; |
| 119 | + access_log /var/log/nginx/access.log main_jwt; |
| 120 | + } |
| 121 | + |
| 122 | + # |
| 123 | + # Backend API example to interact with proxied backend service: |
| 124 | + # |
| 125 | + # - This API resource is protected by access token which is received by IdP |
| 126 | + # after successful signing-in among the frontend site, NGINX Plus and IdP. |
| 127 | + # |
| 128 | + # - To ensure that client requests access the API securely, access token is |
| 129 | + # used for API authorization. |
| 130 | + # + Most of IdP generate an access token for API authorization of IdP's |
| 131 | + # endpoints (like /userinfo) as well as customer's endpoints. |
| 132 | + # + But Azure AD generate two types of access token for API authorization |
| 133 | + # of Microsoft graph API endpoints and customers' endpoints. |
| 134 | + # + Therefore, we recommend that you use $session_jwt for Azure AD and |
| 135 | + # $access_token for most of IdPs such as Cognito, Auth0, Keycloak, Okta, |
| 136 | + # OneLogin, Ping Identity, etc as for now. |
| 137 | + # |
| 138 | + location /v1/api/example { |
| 139 | + auth_jwt "" token=$access_token; # Use $session_jwt for Azure AD |
| 140 | + auth_jwt_key_request /_jwks_uri; # Enable when using URL |
| 141 | + #auth_jwt_key_file $oidc_jwt_keyfile; # Enable when using filename |
| 142 | + |
| 143 | + proxy_set_header Authorization "Bearer $access_token"; |
| 144 | + proxy_pass http://my_backend_app; |
| 145 | + access_log /var/log/nginx/access.log main_jwt; |
| 146 | + } |
| 147 | +} |
| 148 | + |
36 | 149 | # vim: syntax=nginx |
0 commit comments