fix: add missing items field to UserSchemaAttribute#489
Open
sagar-okta wants to merge 1 commit intomasterfrom
Open
fix: add missing items field to UserSchemaAttribute#489sagar-okta wants to merge 1 commit intomasterfrom
sagar-okta wants to merge 1 commit intomasterfrom
Conversation
aniket-okta
approved these changes
Apr 22, 2026
aniket-okta
left a comment
There was a problem hiding this comment.
Security audit, type check, unit + jest tests (114/114), and live API smoke test passed. The items field addition is correct and exactly mirrors the GroupSchemaAttribute pattern.
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
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.
PR Checklist
PR Type
What is the current behavior?
Issue Number: #480
When calling
schemaApi.updateApplicationUserProfilewith a custom attribute oftype: 'array', the SDK strips theitemsfield from the request body. The Okta API then rejects the request with:Root cause: The
itemsproperty was accidentally dropped from theUserSchemaAttributeschema when the OpenAPI spec was updated from v4.0.0 to v5.x. TheUserSchemaAttributeItemsclass and theGroupSchemaAttribute.itemsfield were both retained, butUserSchemaAttribute.itemswas not regenerated.What is the new behavior?
UserSchemaAttributenow includes theitemsfield typed asUserSchemaAttributeItems, consistent withGroupSchemaAttribute.items: { type: 'string' }(or any validUserSchemaAttributeItemsvalue) when settingtype: 'array'on a custom attribute.type: 'array'.Does this PR introduce a breaking change?
Other information
Files changed:
oas-spec/management.yaml— addeditemsfield ($ref: UserSchemaAttributeItems,nullable: true) toUserSchemaAttributeschemasrc/generated/models/UserSchemaAttribute.js— addeditemsentry toattributeTypeMapsrc/types/generated/models/UserSchemaAttribute.d.ts— addedUserSchemaAttributeItemsimport anditemsproperty declaration