Schema Reference
The application schema is used to configure the objects returned from a connector.
Note
-
The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.
-
The schema attributes that are not present by default must be defined as strings if not specified.
The Stytch connector uses the following default correlation and object configurations.
Default Account Schema
Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.
The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.
Default Account ID
SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.
Caution
Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
To resolve issues caused by changing account IDs, reconfigure them to their default values.
The following table lists the default account IDs for this connector:
| Account ID | Schema Object Type |
|---|---|
| member_id | Accounts |
| organization_id | Groups |
| role_id | Roles |
Default Account Attributes
The Stytch connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
| Attribute Name | Description |
|---|---|
| member_id | Unique identifier for the organization member |
| organization_id | Unique identifier of the organization the member belongs to |
| role_id | Display the role of the user. |
| mfa_phone_number | Phone number used for multi-factor authentication |
| default_mfa_method | Default multi-factor authentication method for the member |
| created_at | Timestamp when the member was created |
| password_registrations | Password-based authentication registrations for the member |
| mfa_enrolled | Indicates whether the member is enrolled in multi-factor authentication |
| totp_registrations | Time-based One-Time Password registrations for the member |
| scim_registrations | SCIM provisioning registrations for the member |
| saml_registrations | SAML authentication registrations associated with the member |
| email_address | Email address of the organization member |
| trusted_metadata | Trusted metadata associated with the member |
| updated_at | Timestamp when the member was last updated |
| is_breakglass | Indicates whether the member has emergency breakglass access |
| sso_registrations | Single Sign-On registrations associated with the member |
| webauthn_registrations | WebAuthn authentication registrations for the member |
| name | Display name of the organization member |
| untrusted_metadata | Untrusted metadata associated with the member |
| delete_factor_id | Identifier for the authentication factor to be deleted |
| oauth_registrations | OAuth authentication registrations associated with the member |
| status | Current status of the organization member |
| is_admin | Boolean Attributes tells whether the user is Admin or not |
| is_locked | Determines if the user is locked |
| mfa_phone_number_verified | Determines if the mfa phone number is verified |
| email_address_verified | Determines if the email address is verified |
Default Entitlement Attributes
Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to Managing Entitlements for more information.
Caution
Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.
Default Group Attributes
The Stytch connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.
| Attribute Name | Description |
|---|---|
| organization_id | Unique identifier for the group |
| allowed_auth_methods | List of authentication methods explicitly allowed for the organization. |
| allowed_first_party_connected_apps | First-party applications explicitly allowed to connect to the organization. |
| allowed_mfa_methods | MFA methods that are permitted for user authentication. |
| allowed_oauth_tenants | Map of OAuth tenants that are explicitly allowed for authentication. |
| allowed_third_party_connected_apps | Third-party applications allowed to integrate with the organization. |
| auth_methods | Policy that defines whether all or restricted authentication methods are allowed. |
| claimed_email_domains | Email domains that are claimed and verified by the organization. |
| created_at | Timestamp when the organization record was created. |
| email_allowed_domains | Domains that are allowed for email-based login or registration. |
| email_invites | Defines whether email invitations are allowed for onboarding users. |
| email_jit_provisioning | Policy controlling just-in-time user provisioning via email authentication. |
| first_party_connected_apps_allowed_type | Rule defining whether all or selected first-party apps are allowed. |
| mfa_methods | Policy defining whether all or restricted MFA methods are allowed. |
| mfa_policy | Organization-level MFA requirement |
| oauth_tenant_jit_provisioning | Controls JIT provisioning via OAuth tenant authentication. |
| organization_external_id | External system identifier for the organization. |
| organization_logo_url | URL for the organization’s logo image. |
| organization_name | Display name of the organization. |
| organization_slug | Short unique identifier for the organization used in URLs. |
| rbac_email_implicit_role_assignments | Rules for assigning roles automatically based on email domain |
| scim_active_connection | Currently active SCIM connection (if any). |
| scim_active_connections | List of all active SCIM provisioning connections. |
| sso_active_connections | List of configured and active SSO connections. |
| sso_default_connection_id | Default SSO configuration used for login. |
| sso_jit_provisioning | Policy defining if JIT provisioning via SSO is allowed. |
| sso_jit_provisioning_allowed_connections | SSO connections allowed for JIT provisioning. |
| third_party_connected_apps_allowed_type | Rule defining whether all or selected third-party apps are allowed. |
| trusted_metadata | Custom metadata defined by the organization and trusted by the system. |
| updated_at | Timestamp when the organization record was last updated. |
Default Role Attributes
The Stytch connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.
| Attribute Name | Description |
|---|---|
| role_id | Unique identifier for the role |
| description | Description of the role and its purpose within the system |
| permissions_actions | List of allowed actions for the specified resource (e.g., "*" means all actions) |
| permissions_resource_id | Identifier of the resource to which the actions apply |