Skip to main content

Issue with Provisioning error

  • June 19, 2025
  • 4 replies
  • 106 views

Guys, I am new to Docebo. Started learning Docebo from past 3 weeks.

I have an issue in the production. In the provisioning log, I see this. It started happening from yesterday and I am unaware of how to fix this issue. We are trying to create a new user into Docebo from Entra ID and see this message in the provisioning log details Any steps on how to fix this error? Happening to most of the users from yesterday. We didn’t change any schemas or made any changes.

 

 

 

1. Import urn:ietf:params:scim:schemas:extension:enterprise:2.0:User from Microsoft Entra ID -Success

 

2. Determine if urn:ietf:params:scim:schemas:extension:enterprise:2.0:User is in scope  - Success

 

3. Match urn:ietf:params:scim:schemas:extension:enterprise:2.0:User between Microsoft Entra ID and customappsso   - Success

 

4. Evaluate urn:ietf:params:scim:schemas:extension:enterprise:2.0:User before synchronization  - Success

 

5. Provision urn:ietf:params:scim:schemas:extension:enterprise:2.0:User in customappsso  - Failed

 

Here the properties

userName

markus.guertr@x.com

name.givenName

Mark

name.familyName

Guertr

urn:ietf:params:scim:schemas:extension:docebo:2.0:User:country

BE

Type

urn:ietf:params:scim:schemas:extension:enterprise:2.0:User

Details

Error code

SystemForCrossDomainIdentityManagementServiceIncompatibleFiltering

Error message

StatusCode: Conflict Message: Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details. Web Response: {"schemas":["urn:ietf:params:scim:api:messages:2.0:Error"],"detail":"The request is invalid.","status":409}. This operation was retried 0 times. It will be retried again after this date: 2025-06-19T16:13:07.8954166Z UTC 

4 replies

dklinger
Hero III
Forum|alt.badge.img+11
  • Hero III
  • June 19, 2025

Hi ​@killerwhales - this definitely looks like one to kick up to user support. Many of us have very different authentication approaches, so this may be best to tackle with your CSM.


lrnlab
Hero III
Forum|alt.badge.img+10
  • Hero III
  • June 20, 2025

Can’t say for sure but your country code should probably be the country name instead. Looks like that is the point of failure but what’s odd is you say this worked in the past and just stopped working recently. I would definitely as support if they have any insights on these errors.


Forum|alt.badge.img+2
  • Helper I
  • June 20, 2025

I’m with ​@lrnlab on this! We had issues when not sending the full country name, but you should work with Docebo Support on this one.
Country names in Docebo:
https://help.docebo.com/hc/en-us/articles/10631755218066-List-of-ISO-3166-1-Countries


  • Author
  • Novice I
  • June 20, 2025

The issue is resolved. My other user has changed setting the password automatically at the creation of the user in Docebo. That fixed it after unchecking in Docebo