Custom HTTP parameters for Cloudflare Access are not working #1882

Closed
opened 2026-04-05 16:37:18 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @HaukeMarquardt on 7/3/2023

Hi!

Describe the bug
I am trying to bypass Cloudflare Access using custom header parameters in my GET request. (https://developers.cloudflare.com/cloudflare-one/identity/service-tokens/)
For some reason this does not work with OneUptime. I can see the Cloudflare Access HTML in the response body in the status timeline.

To Reproduce
Steps to reproduce the behavior:

  1. Add an API monitor to a destination which is protected by Cloudflare Access.
  2. Add the service token to the custom header parameters (CF-Access-Client-Id, CF-Access-Client-Secret) of the monitor
  3. See the results

Expected behavior
If the header parameters are set correctly, the response should be the response from your API.

The token is valid. I've already deployed a few self-hosted status tools that use the same token.

*Originally created by @HaukeMarquardt on 7/3/2023* Hi! **Describe the bug** I am trying to bypass Cloudflare Access using custom header parameters in my GET request. (https://developers.cloudflare.com/cloudflare-one/identity/service-tokens/) For some reason this does not work with OneUptime. I can see the Cloudflare Access HTML in the response body in the status timeline. **To Reproduce** Steps to reproduce the behavior: 1. Add an API monitor to a destination which is protected by Cloudflare Access. 2. Add the service token to the custom header parameters (CF-Access-Client-Id, CF-Access-Client-Secret) of the monitor 3. See the results **Expected behavior** If the header parameters are set correctly, the response should be the response from your API. The token is valid. I've already deployed a few self-hosted status tools that use the same token.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#1882