Upgrade to 13.0.2 causes updateUser API to fail from attribute being mastered by a different system about okta-sdk-java HOT 8 CLOSED

Is it possible to get the information from Support on Okta (they have our information there)? The reason why we suspect something happening with the SDK is because this only happened post-upgrade, which means some kind of regression happened with the updateUser and possibly more fields were passed along. Again, not sure why it was only observed in prod, which does point to an environment issue, but Okta support told me to open an issue with you because they couldn't find a difference in our environments.

from okta-sdk-java.

@tiffanykawailee Thanks for submitting this!

This sounds more like an environment related issue to me from initial analysis.

Sounds like the user is imported from or assigned to an app with "profile mastering" enabled (app feature), and is thus read-only. The UI will tell you if a user is Okta sourced or if it's mastered by an app - see https://support.okta.com/help/s/article/How-to-determine-if-a-user-is-profile-mastered-by-Okta?language=en_US

from okta-sdk-java.

Hello! The users have profile mastering, but the thing is that the field isn't mastered by that profile, which means it should be updated.

This update worked in previous versions, but not our current one. Additionally, other users mastered by another profile worked just fine for the update, which to me indicates some sort of bug with the SDK for a certain edge case. Is it possible for you to investigate it? We'd been holding off this update, and okta support sent me here for the SDK team to investigate this further.

from okta-sdk-java.

My only concern is that if its a SDK bug, it should affect all your environments and not just the PROD. You mentioned this SDK upgrade worked in your non-PROD environments right? I can investigate this on SDK side from my end, sure but it'd be hard for me to know/reproduce what kind of org settings and feature flags your orgs have and the app settings related to "profile mastering" are configured in your org. Also note that this error is returned by the Okta backend and all the SDK does is to relay it to the user.

from okta-sdk-java.

@tiffanykawailee Thanks, I've found the bug in code. Will fix it and release patch SDK version 14.0.1 soon. Would you be able to upgrade to the 'to-be-released' 14.0.1 version?

from okta-sdk-java.

We should be able to update to 14.0.1. thank you! Are you able to provide any details about why this was only observed in certain environments, or is that related to our configurations?

Additionally -- can you let me know what breaking changes exist from 13 to 14?

from okta-sdk-java.

@tiffanykawailee I do not know enough about the environment differences on your end to explain why the behavior should be different in your PROD vs non-PROD environments. Good news is I was able to reproduce this issue in my environment and hence was able to debug this and merge the fix.

Breaking changes would come in to picture while upgrading from 13.x to 14.x (see release notes for the list of changes).

In order to minimize your effort now, I would release a patch version 13.0.2 shortly. You should be able to easily upgrade to 13.0.2 to get past this issue.

from okta-sdk-java.

13.0.3 has just been released with the fix.

Please feel free to reopen issue if you have any followups.

from okta-sdk-java.