Skip to content

feat: add app user-profile schema tools - #73

Open
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:feat/app-user-schema-tools
Open

feat: add app user-profile schema tools#73
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:feat/app-user-schema-tools

Conversation

@mjdavidson

Copy link
Copy Markdown

There was no way to add custom attributes to an application's user-profile schema (the Profile Editor "Add Attribute" step) — only read-only inspection. Adds get_app_user_schema and add_app_user_schema_attribute; the write posts to /api/v1/meta/schemas/apps/{id}/default through the request executor (the schemas endpoint has no typed SDK wrapper) and is a partial update that leaves existing custom properties intact. Uses the Schemas API scopes (okta.schemas.read/okta.schemas.manage).\n\nTests: tests/test_app_user_schema.py.

There was no way to define custom attributes on an application's user profile
(the Profile Editor 'Add Attribute' step), so SSO/provisioning flows that map a
SAML attribute statement to a real profile field (e.g. user.employeeNumber)
could not be set up through the server — only read-only inspection existed.

Add get_app_user_schema (typed GET) and add_app_user_schema_attribute, which
posts a custom property to /api/v1/meta/schemas/apps/{id}/default. The schemas
endpoint has no typed SDK write wrapper, so the update goes through the request
executor; it is a partial update that leaves existing custom properties intact.
These use the Schemas API scopes (okta.schemas.read / okta.schemas.manage), with
registry entries and README updates.
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