SCIM Entra ID - 404 on PATCH #252

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

Originally created by @arthur-lbchn on 11/24/2025

Describe the bug

Hi, I've successfully connected SSO and SCIM to Entra ID.

When trying to use "Provision on Demand", the Entra ID get 404 response from OneUptime on PATCH

Image

Below you can see the logs from the docker:

ingress-1                  | 20.190.129.80 - - [24/Nov/2025:20:40:12 +0000] "GET /identity/scim/v2/a937478c-19b7-4c73-8481-1ff2e07b90b6/Users?filter=userName+eq+%223e59e27b-68ad-41f5-bb0e-dadf130e2ac8%22 HTTP/1.1" 200 130 "-" "-" "-"
ingress-1                  | 20.190.129.80 - - [24/Nov/2025:20:40:12 +0000] "GET /identity/scim/v2/a937478c-19b7-4c73-8481-1ff2e07b90b6/Users?filter=userName+eq+%22REDACTED%40REDACTED%22 HTTP/1.1" 200 790 "-" "-" "-"
ingress-1                  | 20.190.129.80 - - [24/Nov/2025:20:40:12 +0000] "PATCH /identity/scim/v2/a937478c-19b7-4c73-8481-1ff2e07b90b6/Users/8815e2e2-533d-496d-a2bd-2c9504d908ca HTTP/1.1" 404 266 "-" "-" "-"

While the user is created, it's important to get Entra ID success code and prevent unwanted false-positive alerting.

To Reproduce
Steps to reproduce the behavior:
Test users sync between Entra ID and OpenUptime by using "Provision on demand" feature

Expected behavior
Entra ID get proper 200 response on the latest PATCH

Desktop (please complete the following information):

  • MacOS
  • Browser Edge

Deployment Type
Self hosted (Docker Compose)
API: 9.0.5598 (8ebe034)
Dashboard: 9.0.5598 (8ebe034)

*Originally created by @arthur-lbchn on 11/24/2025* **Describe the bug** Hi, I've successfully connected SSO and SCIM to Entra ID. When trying to use "Provision on Demand", the Entra ID get 404 response from OneUptime on PATCH <img width="1802" height="932" alt="Image" src="https://github.com/user-attachments/assets/7168cce7-4e7d-44c2-a2d8-7f45c59c2ce0" /> Below you can see the logs from the docker: ``` ingress-1 | 20.190.129.80 - - [24/Nov/2025:20:40:12 +0000] "GET /identity/scim/v2/a937478c-19b7-4c73-8481-1ff2e07b90b6/Users?filter=userName+eq+%223e59e27b-68ad-41f5-bb0e-dadf130e2ac8%22 HTTP/1.1" 200 130 "-" "-" "-" ingress-1 | 20.190.129.80 - - [24/Nov/2025:20:40:12 +0000] "GET /identity/scim/v2/a937478c-19b7-4c73-8481-1ff2e07b90b6/Users?filter=userName+eq+%22REDACTED%40REDACTED%22 HTTP/1.1" 200 790 "-" "-" "-" ingress-1 | 20.190.129.80 - - [24/Nov/2025:20:40:12 +0000] "PATCH /identity/scim/v2/a937478c-19b7-4c73-8481-1ff2e07b90b6/Users/8815e2e2-533d-496d-a2bd-2c9504d908ca HTTP/1.1" 404 266 "-" "-" "-" ``` While the user is created, it's important to get Entra ID success code and prevent unwanted false-positive alerting. **To Reproduce** Steps to reproduce the behavior: Test users sync between Entra ID and OpenUptime by using "Provision on demand" feature **Expected behavior** Entra ID get proper 200 response on the latest PATCH **Desktop (please complete the following information):** - MacOS - Browser Edge **Deployment Type** Self hosted (Docker Compose) API: 9.0.5598 (8ebe034) Dashboard: 9.0.5598 (8ebe034)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#252