Skip to content

feat: add tools to read and set a user's app-specific profile - #74

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

feat: add tools to read and set a user's app-specific profile#74
mjdavidson wants to merge 1 commit into
okta:mainfrom
mjdavidson:feat/app-user-profile-tools

Conversation

@mjdavidson

Copy link
Copy Markdown

Custom attributes can be defined on an app's user-profile schema, but there was no way to populate a specific assigned user's values for them. Adds get_app_user and update_app_user_profile (e.g. set employeeNumber for a user on an app). The SDK's AppUserUpdateRequest is an ambiguous oneOf for a profile-only body, so these use the request executor against /api/v1/apps/{id}/users/{userId}.\n\nTests: tests/test_app_user_profile.py.

Custom attributes can be defined on an app's user-profile schema, but there was
no way to populate a specific assigned user's values for them (e.g. set
employeeNumber=E-12345 for one user on an app), so per-user app profile data
couldn't be managed through the server.

Add get_app_user (GET /api/v1/apps/{id}/users/{userId}) and
update_app_user_profile (POST same path with a {"profile": {...}} body). The
SDK's AppUserUpdateRequest is an ambiguous oneOf (a profile-only dict matches
both the profile and credentials payloads, so from_dict raises), so these go
through the request executor and return Okta's JSON verbatim. Reads gate on
okta.apps.read, writes on okta.apps.manage.
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