ApplicationUsers
Assigned users for an app.
View Specific Information
Required Scopes
To query this view, Scope must include okta.apps.read.
Select
The add-in uses the Okta API to process WHERE clause conditions built with the following columns and operators.- Id supports the '=' operator
- UserName supports the '=' and 'LIKE (starts with)' operators
- AppId supports the '=' operator
- Search supports the '=' and 'LIKE (starts with)' operators
All other filters are processed client-side within the add-in.
For example, the following query is processed server-side:
SELECT * FROM ApplicationUsers WHERE AppId = '0oafxqCAJWWGELFTYASJ' SELECT * FROM ApplicationUsers WHERE AppId='0oajy670d0I8ic9T55d7' AND Search='[email protected]'
Columns
Name | Type | Description |
Id [KEY] | String | Id of the user |
ExternalId | String | ID of the user in the target app linked to the Okta Application User object |
Created | Datetime | When the item was created |
LastUpdated | Datetime | When the item was last updated |
Scope | String | The scope of the user |
Status | String | Status of the user |
StatusChanged | Datetime | When the status was last updated |
PasswordChanged | Datetime | When the password was last updated |
SyncState | String | Status of the API token |
LastSync | Datetime | When the item was last synced |
UserName | String | The user's username in the app |
Profile | String | Aggregate of the profile |
AppId [KEY] | String | Application Id |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements, and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
Search | String | Filters the profile's email and, for non-ODIC apps, the firstName and lastName |