application_user_schemas

Creates, updates, deletes, gets or lists an application_user_schemas resource.

Overview

Name	application_user_schemas
Type	Resource
Id	okta.meta.application_user_schemas

Fields

The following fields are returned by SELECT queries:

get_application_user_schema

successful operation

Name	Datatype	Description
id	string	URI of user schema
name	string	Name of the schema
$schema	string	JSON schema version identifier
_links	object	Specifies link relations (see Web Linking) available using the JSON Hypertext Application Language specification. This object is used for dynamic discovery of related resources and lifecycle operations.
created	string	Timestamp when the schema was created
definitions	object	User profile subschemas The profile object for a user is defined by a composite schema of base and custom properties using a JSON path to reference subschemas. The #base properties are defined and versioned by Okta, while #custom properties are extensible. Custom property names for the profile object must be unique and can't conflict with a property name defined in the #base subschema.
lastUpdated	string	Timestamp when the schema was last updated
properties	object	User Object Properties
title	string	User-defined display name for the schema
type	string	Type of root schema

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
get_application_user_schema	select	subdomain		Retrieves the default schema for an app user. The User Types feature does not extend to apps. All users assigned to a given app use the same app user schema. Therefore, unlike the user schema operations, the app user schema operations all specify default and don't accept a schema ID.
update_application_user_profile	update	subdomain		Updates the app user schema. This updates, adds, or removes one or more custom profile properties or the nullability of a base property in the app user schema for an app. Changing a base property's nullability (for example, the value of its required field) is allowed only if it is nullable in the default predefined schema for the app. > Note: You must set properties explicitly to null to remove them from the schema; otherwise, POST is interpreted as a partial update. The User Types feature does not extend to apps. All users assigned to a given app use the same app user schema. Therefore, unlike the user schema operations, the app user schema operations all specify default and don't accept a schema ID.

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

Name	Datatype	Description
subdomain	string	The domain of your organization. This can be a provided subdomain of an official okta domain (okta.com, oktapreview.com, etc) or one of your configured custom domains. (default: my-org)

SELECT examples

get_application_user_schema

Retrieves the default schema for an app user.

The User Types feature does not extend to apps. All users assigned to a given app use the same app user schema. Therefore, unlike the user schema operations, the app user schema operations all specify default and don't accept a schema ID.

SELECT
id,
name,
$schema,
_links,
created,
definitions,
lastUpdated,
properties,
title,
type
FROM okta.meta.application_user_schemas
WHERE subdomain = '{{ subdomain }}' -- required
;

UPDATE examples

update_application_user_profile

Updates the app user schema. This updates, adds, or removes one or more custom profile properties or the nullability of a base property in the app user schema for an app. Changing a base property's nullability (for example, the value of its required field) is allowed only if it is nullable in the default predefined schema for the app.

> Note: You must set properties explicitly to null to remove them from the schema; otherwise, POST is interpreted as a partial update.

The User Types feature does not extend to apps. All users assigned to a given app use the same app user schema. Therefore, unlike the user schema operations, the app user schema operations all specify default and don't accept a schema ID.

UPDATE okta.meta.application_user_schemas
SET 
data__definitions = '{{ definitions }}',
data__properties = '{{ properties }}',
data__title = '{{ title }}'
WHERE 
subdomain = '{{ subdomain }}' --required
RETURNING
id,
name,
$schema,
_links,
created,
definitions,
lastUpdated,
properties,
title,
type
;