Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
Support OIDC/OAuth Bearer Authentication behind trusted TLS-terminating reverse proxies
Domino should allow administrators to configure trusted reverse proxies/load balancers and recognize the original request scheme through the standardized Forwarded: proto=https header defined in RFC 7239 and/or the widely used X-Forwarded-Proto: https header. Forwarded scheme information should only be trusted when the immediate peer is explicitly configured as a trusted proxy, consistent with the security considerations in RFC 7239.
This would allow deployments where TLS terminates at a load balancer while retaining Domino's bearer-token transport security requirements defined in RFC 6750, rather than globally allowing bearer authentication over unprotected HTTP.