oauth2-cc
should use the proxy configuration for getOidcTokenClientCredentials
#4713
Open
2 tasks done
Labels
area:monitor
Everything related to monitors
feature-request
Request for new features to be added
help wanted
May need your help to test or answer
type:enhance-existing
feature wants to enhance existing monitor
🛡️ Security Policy
📝 Describe your problem
I have a monitor protected by JWT based authentication. I have configured the endpoint/clientID/Secret etc. However, the monitor fails with error "The oauth config is invalid, ENOTFOUND error".
Troubleshooting this further, the token endpoint can be reached via curl from the Docker container running uptime kuma without issue. Both the clientID and secret are valid and have been tested via Postman calls. This rules out any DNS related problems, as curl as well as postman are able to resolve this endpoint.
I also have a proxy setup that has been configured to route specific traffic. What i suspect is that nodeJS is unable to route the traffic to the JWT endpoint as it is not aware of the proxy?
Has anyone else faced similar issues with JWT + Proxy?
📝 Error Message(s) or Log
"The oauth config is invalid, ENOTFOUND error".
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Suse 15 with Kuma docker image
🌐 Browser
Firefox 115.10.0esr (64-bit)
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: