Skip to content

fix(GroupProfile): restore custom group-profile attribute extensibility#500

Open
eleonoratennyson wants to merge 1 commit into
okta:masterfrom
eleonoratennyson:eqt/sync-org-catalog-to-okta
Open

fix(GroupProfile): restore custom group-profile attribute extensibility#500
eleonoratennyson wants to merge 1 commit into
okta:masterfrom
eleonoratennyson:eqt/sync-org-catalog-to-okta

Conversation

@eleonoratennyson

@eleonoratennyson eleonoratennyson commented Jun 24, 2026

Copy link
Copy Markdown

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Adding Tests
  • Build related changes
  • CI related changes
  • Documentation changes
  • Other... Please describe:

What is the current behavior?

GroupProfile is not marked x-okta-extensible, so ObjectSerializer strips
custom group-profile attributes — those added via the Schemas API
on both serialize and deserialize. Custom attributes therefore never reach Okta
on writes and are dropped on reads. This worked through 6.6.0 (#365) and
regressed afterwards. UserProfile and OktaUserGroupProfile remain extensible;
GroupProfile supports schema extensions the same way and should be too.

Issue Number: #238

What is the new behavior?

GroupProfile is added to the force-extensible list in scripts/fixSpec.cjs
(alongside UserProfile) and the SDK regenerated. This restores, on
GroupProfile, the CustomAttributeValue import, the typed index signature, and
static readonly isExtensible = true, so custom attributes round-trip through
ObjectSerializer again.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@eleonoratennyson eleonoratennyson force-pushed the eqt/sync-org-catalog-to-okta branch from 0d27c11 to 5736b0d Compare June 24, 2026 22:14
GroupProfile lost its extensibility after 6.6.0 (okta#365): because it is not marked
x-okta-extensible, ObjectSerializer strips custom group-profile attributes (those
added via the Schemas API, e.g. an org-chart id) on both serialize and
deserialize, so they never reach Okta on writes and are dropped on reads.

Add GroupProfile to the force-extensible list in scripts/fixSpec.cjs — matching
UserProfile and OktaUserGroupProfile, which remain extensible — and regenerate.
This restores the typed index signature and `static readonly isExtensible = true`
so custom attributes round-trip again.

Refs okta#238, okta/okta-sdk-java#1642.
@eleonoratennyson eleonoratennyson force-pushed the eqt/sync-org-catalog-to-okta branch from 5736b0d to f58dd81 Compare June 24, 2026 22:19
@eleonoratennyson eleonoratennyson marked this pull request as ready for review June 24, 2026 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant