OKTA-860375 - adding setters for the fields which were 'null'#1620
Merged
prachi-okta merged 1 commit intomasterfrom Apr 15, 2025
Merged
OKTA-860375 - adding setters for the fields which were 'null'#1620prachi-okta merged 1 commit intomasterfrom
prachi-okta merged 1 commit intomasterfrom
Conversation
prachi-okta
requested review from
BinoyOza-okta,
aditya-okta,
aniket-okta and
pranav-okta
BinoyOza-okta
approved these changes
Apr 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue(s)
https://oktainc.atlassian.net/browse/OKTA-860375
Description
Customer is using version 20.0.0 of the Java SDK and are seeing a problem where a custom application using that SDK reads a list of groups and in the profile, the dn and windowsDomainQualifiedName field for all of the groups of type APP_GROUP are showing up as NULL in the brokered Java object. If they hit the rest API directly hitting the same endpoint, they see the dn and windowsDomainQualifiedName populated in the JSON for all of the APP_GROUP profiles.
Solution
Added setters for the fields being populated as null.
Category
Signoff