`oauth2-cc` should use the proxy configuration for `getOidcTokenClientCredentials`

⚠️ Please verify that this question has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project 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

• Runtime: 20.10.17-ce
• Database: Sqlite/embedded
• Filesystem used to store the database on: ext4
• number of monitors: 108