Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Unable to Provision Users via SCIM

Written By

Madeleine Clay

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • User provisioning via SCIM is failing.
  • Liferay logs indicate a permission error: 
    ERROR [org.wso2.charon3.core.protocol.endpoints.AbstractResourceManager] Unable to provision a portal user for null
org.wso2.charon3.core.exceptions.CharonException: Unable to provision a portal user for null
[...]
Caused by: com.liferay.portal.kernel.security.auth.PrincipalException$MustHavePermission: User \[USER_ID] must have UPDATE permission for com.liferay.portal.kernel.model.User \[USER_ID]
[...]

Environment

  • 2024.Q1

Resolution

Important

This feature is behind a beta feature flag in 2024.Q1.

  • The issue is caused by a known bug  where the OAuth 2 access token used by SCIM is generated with guest user permissions instead of the permissions of the user who generated the SCIM access token.
  • To resolve this issue, apply the fix for LPD-33284
    • either upgrading to 2024.Q4.0 or above
    • Or open a help center ticket to request a hotfix at your current patch level

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?