Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions about [NginxPlus + nginx-openid-connect] proxy use on the intranet #53

Open
jiruisong opened this issue Jun 7, 2022 · 3 comments

Comments

@jiruisong
Copy link

jiruisong commented Jun 7, 2022

Hello

Our company is intended [NginxPlus + nginx-openid-connect] to be used in the intranet

The following problem arises

图片

errorlog:
「503 login.microsoftonline.com could not be resolved」
「js: OIDC unexpected response from IdP when sending authorization code (HTTP 502). 」

Question:

1. Is there a setting like "OIDCOutgoingProxy" in NginxPlus or in nginx-openid-connect module? (Apache+OIDC has such a configuration parameter)

2. Why NginxPlus cannot analyze "login.microsoftonline.com"? Error log: "503 login.microsoftonline.com could not be resolved".

thanks a lot

@route443
Copy link
Contributor

Hi @jiruisong ,

  1. If your environment requires the use of a tunneling proxy server when communicating between the NGINX and the identity provider (login.microsoftonline.com), then no, we don't support this.

  2. Based on this error message, it's hard for me to say what the root cause is. If you are sure that the DNS server specified in the resolver directive is functioning as expected and can successfully resolve the "login.microsoftonline.com" fqdn, try disabling the IPv6 address lookup (the ipv6=off parameter can be specified), this may help in some cases. In any case, this error has nothing to do with "nginx-openid-connect" module, so if the problem persists, you can contact NGINX Plus support using the appropriate channels.

@souravGuptaSg
Copy link

Hi @jiruisong ,
Same issue is being faced by my team on configuring OIDC in nginx plus with IDP (using Auth Zero),
Did you get any solution over it? It would be helpful if you could share the same

@llomgui
Copy link

llomgui commented Apr 17, 2023

Hello @jiruisong @souravGuptaSg,

Did you find a solution?

About the resolver, I added a configmap to fix the issue:

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-config
  namespace: nginx-ingress
data:
  resolver-addresses: dns-default.openshift-dns.svc.cluster.local

About the proxy, I could not find it yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants