Comments (8)
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.
Related Issues (20)
- Private Key is interpreted as PEMKeyPair instead of PrivateKeyInfo HOT 3
- Consistently thrown NoHttpResponseException's in 13.0.3 HOT 3
- An attempt to remove profile attribute value does not succeed HOT 2
- 13.0.2 missing UTF-8 support in Azure HOT 4
- Null LinksSelf in VerifyUserFactorResponse HOT 1
- Missing "List groups assigned to application" HOT 5
- OAUTH_AUTHORIZATION_POLICY PolicyType missing in latest spec HOT 9
- With 14.0.0 the application id is always null upon create HOT 2
- ClassNotFoundException with current dependencies in Gradle build HOT 4
- Okta Verify Fast Pass as an enrolled Factor is not returned HOT 8
- UserProfile equals() does not return true when objects are equal HOT 1
- `IdentityProviderApi` cannot properly deserialize `/ipds` responses HOT 1
- Create authorization server policy with type OAUTH_AUTHORIZATION_POLICY get error HOT 3
- IdP Discovery Policy not returned in listPolicyRules() HOT 2
- GroupsAPI - Custom group profile attributes missing HOT 3
- Several outdated dependencies
- OpenAPI spec missing some default role type HOT 3
- Invalid session HOT 3
- IdpPolicyRuleActionProvider needs the ability to set the provider id to be useful for creating IDP Routing Rules HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from okta-sdk-java.