uptime-kuma: OAuth config invalid - token_endpoint_auth_method invalid or missing

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

  • I checked and didn’t find similar issue

🛡️ Security Policy

Description

While setting up OAuth Authentication for Monitoring I keep receiving

API Endpoint [DOWN] The oauth config is invalid. missing, or unsupported, token_endpoint_auth_method

There is no way to set the value, which would then default to client_secret_basic here: https://github.com/louislam/uptime-kuma/blob/c4e222d1e6bc3846d6672368ae30301a796fa39e/server/util-server.js#L75

The method is supported (I’m trying to connect to an Azure service) The credentials are working (testing with postman). (https://login.microsoftonline.com/9188040d-6c67-4c5b-b112-36a304b66dad/v2.0/.well-known/openid-configuration)

I couldn’t find any documentation about the settings ir limitation of the current oauth implementation to check or compare my settings.

👟 Reproduction steps

  • Select OAuth as method under “Authentication”
  • Select either Header or Body as authentication Method
  • Enter https://login.microsoftonline.com/9188040d-6c67-4c5b-b112-36a304b66dad/oauth2/v2.0/token as token_url
  • Enter random string for Client_ID
  • Enter random string for Client_Secret
  • Enter openidor https://api.businesscentral.dynamics.com/.default as Scope

👀 Expected behavior

Fail with invalid credentials / or pass with valid credentials

😓 Actual Behavior

Receiving an error message: The oauth config is invalid. missing, or unsupported, token_endpoint_auth_method

🐻 Uptime-Kuma Version

1.23.1

💻 Operating System and Arch

Debian 12

🌐 Browser

Firefox

🐋 Docker Version

24.0.5

🟩 NodeJS Version

No response

📝 Relevant log output

`Failing: The oauth config is invalid. missing, or unsupported, token_endpoint_auth_method`

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 21 (8 by maintainers)

Most upvoted comments

I’m on it but this week is tight on my side. Will report back on the end of the week.

The bug with monitor.oauth_auth_method is already noted

@TargetCrafter Just wanting to let you know that I will delete the hegerdes/testing:uptime-kuma-3727 in the next month. This should not be a problem since it is fixed in master and a new release was published some time ago.

I’m running the docker version. I’ll see if I find the time in the next days to set up npm. And run it as a dev server.

@s256

You can test it with this special docker image without setting up an environment.

docker run --rm -it -p 3000:3000 -p 3001:3001 --pull always \ 
-e 'UPTIME_KUMA_GH_REPO=hegerdes:fix-oauth2-auth-method-setting' \
louislam/uptime-kuma:pr-test

Go to http://localhost:3000 after started.

More info: https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests