# SCIM attribute mapping

**URL:** <https://community.sonarsource.com/t/scim-attribute-mapping/148003>\
**Category:** SonarQube Server / Community Build\
**Tags:** authentication\
**Created:** [September 3, 2025, 8:25am UTC](https://community.sonarsource.com/t/scim-attribute-mapping/148003 "2025-09-03T08:25:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![andi](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@andi](https://community.sonarsource.com/u/andi)\
**Post date:** [September 3, 2025, 8:25am UTC](https://community.sonarsource.com/t/scim-attribute-mapping/148003/1 "2025-09-03T08:25:36Z")

</div>

Must-share information (formatted with [Markdown](https://commonmark.org/help/)):

- SonarQube Server Enterprise 2025.1.3
- how is SonarQube deployed: zip
- Provision user accounts with SCIM and Entra ID
- Succesfully configured SAML
- Configured SCIM on SonarQube and Entra ID but getting errors for some users

We have configured SCIM on SonarQube and on the Entra ID server for the majority of user this works correct.

But some users are not created and we get an error in the web-logs:  
_ **Error** while processing request: User name must not be blank_

For some other users the last name is set to the string “null”.

Can you please provide some information which _customappsso Attribute_ is used for which purpose in SonarQube.

Thank you,  
Andreas

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [September 4, 2025, 8:58am UTC](https://community.sonarsource.com/t/scim-attribute-mapping/148003/2 "2025-09-04T08:58:41Z")

</div>

Hello,

> [@andi](#):
>
> Can you please provide some information which _customappsso Attribute_ is used for which purpose in SonarQube.

These are attributes that you define yourself in the [SonarQube SAML configuration](https://docs.sonarsource.com/sonarqube-server/2025.1/instance-administration/authentication/saml/overview/#settings).

It appears that some users are missing these required attributes, which is preventing them from logging in. I recommend checking the SAML assertion attributes for affected users and comparing them to those that are working. This will help you identify any discrepancies and adjust the IdP configuration accordingly.

---

<div class="post-metadata">

**Author:** ![andi](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@andi](https://community.sonarsource.com/u/andi)\
**Post date:** [September 4, 2025, 11:04am UTC](https://community.sonarsource.com/t/scim-attribute-mapping/148003/3 "2025-09-04T11:04:27Z")

</div>

Hi Colin,

thank you for your reply.  
But we want to introduce SCIM and are facing problems with the mappings.

The docs you mentioned are for SAML. Are the same attributes available for SCIM?

Thank you,  
Andreas

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [September 4, 2025, 1:04pm UTC](https://community.sonarsource.com/t/scim-attribute-mapping/148003/4 "2025-09-04T13:04:04Z")

</div>

Hey there.

Alright, I understand your question a bit better after doing some research!

> [@andi](#):
>
> _ **Error** while processing request: User name must not be blank_
> 
> For some other users the last name is set to the string “null”.

SonarQube uses  
`givenName` for the first name  
`familyName` for the last name.  
`userName` is the user’s… username.

This is not exhaustive, but seems like the kind of thing we should have documented. So I’ll ping the team.