SCIM is Provisioning Attributes that are not mapped

Loading

Skip to Navigation Skip to Main Content

Search

Search

Select Language

0D54z0000AIeBo1CQFOkta Classic EngineIntegrationsAnswered2025-01-31T22:56:59.000Z2025-01-12T17:17:20.000Z2025-01-31T22:56:59.000Z

User17367016023565952420 (Customer) asked a question.

January 12, 2025 at 5:17 PM

SCIM is Provisioning Attributes that are not mapped

I added the Bonusly app to my Okta account and set it up for provisioning. My Okta users were provisioned successfully and with only the attributes I mapped in the settings for Okta --> Bonusly.

I then updated the user record on the Bonusly side to set a hire date and birth date in Bonusly. Next I added a department value to the user in Okta which triggered an update of the user via SCIM to Bonusly. This update mysteriously included hire date and birth date information in the payload which I do not have mapped in the application settings. These values match the values I set on the user in Bonusly and are returned as part of the SCIM GET user response from the Bonusly API.

/help/servlet/rtaImage?refid=0EM4z000007Ipml

It appears that Okta is retrieving the user information from Bonusly via the API and sending that with the user update requests to Bonusly even though I do not have those attributes mapped in my application settings. Bonusly --> Okta import setting is also set to "Never" and no mappings are setup for these fields there either.

Is this normal behavior or some kind of bug?

Integrations

Top Rated Answers

Mihai N. (Okta, Inc.)
a year ago
Hi @User17367016023565952420 (Customer) , Thank you for reaching out to the Okta Community!

The SCIM Provisioning part of the app is partner-built by Bonusly, so I'm not sure what control the Okta side will have on the way the information is queried via the Bonusly API.
I've checked the back-end for the default configuration of the app and profile schema does not list the hire/birth date attributes.
I haven't been able to locate any similar reports, so far.
The setup guide provided for the Provisioning settings for the app that is under the Okta Admin UI seems to point towards a Google doc that is no longer available.
I found a different one online but it does not go into details.
https://help.bonus.ly/en/articles/3715183-how-to-configure-saml-sso-and-user-provisioning-with-okta

If you have a paid account with us, I recommend opening a case so the support team check to see if there's anything on the Okta side that can be changed to prevent this.
That being said, I also recommend reaching out to support@bonus.ly to inquire about this.

If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.

Hope my answer helps!

--
Help others in the community by liking or hitting Select as Best if this response helped you.
Expand Post
Selected as Best

All Answers

Mihai N. (Okta, Inc.)
a year ago
Hi @User17367016023565952420 (Customer) , Thank you for reaching out to the Okta Community!

The SCIM Provisioning part of the app is partner-built by Bonusly, so I'm not sure what control the Okta side will have on the way the information is queried via the Bonusly API.
I've checked the back-end for the default configuration of the app and profile schema does not list the hire/birth date attributes.
I haven't been able to locate any similar reports, so far.
The setup guide provided for the Provisioning settings for the app that is under the Okta Admin UI seems to point towards a Google doc that is no longer available.
I found a different one online but it does not go into details.
https://help.bonus.ly/en/articles/3715183-how-to-configure-saml-sso-and-user-provisioning-with-okta

If you have a paid account with us, I recommend opening a case so the support team check to see if there's anything on the Okta side that can be changed to prevent this.
That being said, I also recommend reaching out to support@bonus.ly to inquire about this.

If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.

Hope my answer helps!

--
Help others in the community by liking or hitting Select as Best if this response helped you.
Expand Post
Selected as Best
User17367016023565952420 (Customer)
a year ago
Thanks for the quick reply!

I actually work FOR Bonusly and opened this thread because I couldn't find another way to contact Okta support about the issue. (We lost access to our developer account and I'm still trying to figure out how to contact someone to restore it.)

We have multiple Bonusly customers that use Okta which is how we became aware of the issue. What I can say is that our integration isn't doing anything out of the ordinary.

I don't understand why Okta would be taking this date information out of a GET request to our SCIM user endpoint and sending it back to us on updates for the same user when no attribute mappings have been established for it in Okta.
Expand Post
- Mihai N. (Okta, Inc.)
  a year ago
  Acknowledged.
  Typically if you are dealing with a new integration the Okta Network, you would have to discuss the implementation with our colleagues from the OIN team via oin@okta.com, but in this case if the app is already integrated, please email our colleagues at developers@okta.com and explicitly mention that you are the application vendor (ISV) looking to troubleshoot the app.
  
  Regards.
  --
  Help others in the community by liking or hitting Select as Best if this response helped you.
  
  Expand Post
User17367016023565952420 (Customer)
a year ago
Thank you!
Expand Post

This question is closed.

Recommended content

Forum

SCIM provisioning fails when custom attribute 'roles' is mapped

Forum

Mapping attribute for SCIM provisioning using an Expression

Forum

Warnings appear that required fields are not mapped,

Forum

SCIM Provisioning - New app's provisioning setup not mapping options correctly

Loading

SCIM is Provisioning Attributes that are not mapped