---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Client type configuration for OAuth and SSO records

# Client type configuration for OAuth and SSO records {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure the Client Type field for OAuth and SSO record related configurations.

When establishing sessions for various login types such as Web UI (interactive login), Iframe Embedded, Embedded or Integration, you can configure the client type for the OIDC (OAuth Entity), SAML, and Digest records that are used for
various login.

The client type choices are as follows:

* Iframe Embedded: Can be used for interactive ServiceNow instance that resides in an Iframe in the third-party websites. For example, if there is a sensitive table (sys_user table - phone number of the user), as admin you can configure the ACL with the security attribute (Iframe Embedded) set to false, to avoid the user accessing the data (table information) on the Iframe Embedded session in the third party.
* Integration as a User: Can be used for Virtual Agent chatbot that are installed in desktop apps such as Slack, Teams, and so on.
* Integration as a Service: Can be used for machine to machine integration (communication between services).

{#client-type__ul_ryy_5xz_zbc}  
Note:  
* For OIDC (OAuth Entity): All the choices are available.
* For SAML and Digest: Only Iframe embedded. You must edit the form and add the Client Type field to the record and select the Iframe Embedded client type.
* If the Client Type selected is none, then there is no classification of the session.
{#client-type__ul_tl2_2zz_zbc}

Use the client type field in every record created for OIDC (OAuth Entity), SAML, and Digest. This enables you to have a better control over each login method that has the same configurations but is distinguished by
the client type.

After configuring the field, whenever a user logs in from the corresponding configuration (OAuth or SSO), after the authentication is successful, the session is considered based on the configured client type and accordingly the session
timeout is used.

For the current session, the corresponding security attributes are included or can be used to help prevent users from accessing table specific information within the selected client type. For more information, see [OOB (Out-of-Box) Security Attributes](https://www.servicenow.com/docs/ttFdHaDPL3bNPE8XA0df6w "Commonly used, generalized security attributes roles ready for use.").

## Session timeout for the client types {#client-type__section_wtf_bnj_ybc}

The following system properties are related to session timeout for the various client types:

* <kbd class="ph userinput">glide.session_timeout.iframe_embedded</kbd>
* <kbd class="ph userinput">glide.session_timeout.integration_as_a_user</kbd>
* <kbd class="ph userinput">glide.session_timeout.integration_as_a_service</kbd>
{#client-type__ul_gkq_dnj_ybc}