> For AI agents: [llms.txt](https://docs.trustedauth.com/llms.txt) provides a Markdown index of this documentation.

# Preconfigured OIDC and OAuth applications

You can configure your applications so that they are accessible to Identity as a Service accounts through OpenID Connect (OIDC) authentication and OAuth authorization. Identity as a Service supports both the Code (or Basic) Authentication Flow use case and the Implicit Authentication Flow use case.

OIDC issues ID tokens and access tokens to:

- Allow desktop and mobile devices to confirm an end-user's identity based on the authentication method performed by Identity as a Service.
- Obtain the Userinfo data.

OAuth issues access tokens that allow client applications to access resource server APIs on behalf of a user using access tokens.

Both OIDC and OAuth access tokens can also be issued with refresh tokens. See [Manage OIDC and OAuth tokens](/docs/applications-and-sso/manage-applications/integrate-oidc-and-oauth-cloud-applications/manage-oidc-and-oauth-tokens.md) for more information about OIDC and OAuth tokens.

Identity as a Service also supports the Client Credentials Flow use case that can be used with direct client application requests to resource server APIs without a user present.

warning

The Implicit grant type has security implications. It is currently supported with OpenID Connect (OIDC) and not with OAuth. It is deprecated and will be removed in a future Identity as a Service release. Applications using the Implicit grant type should use the Authorization Code grant type with Proof Key for Code Exchange (PKCE) instead.

## Supported request parameters

In addition to the standard OIDC request parameters, OIDC and OAuth support the following ones:

- login_hint
- claims
- acr_values
- amr_values
- audience or resource
- org_id

OIDC and OAuth do not support the following OIDC request parameters:

- display
- id_token_hint
- ui_locales

OIDC and OAuth do not support the following features:

- Introspection
- Dynamic Client Registration
- Token Encryption

## Topics in this section

[📄️ConnectWise Home You can configure ConnectWise Home to use IDaaS for multifactor authentication. ConnectWise Home is a business process automation platform (see https://www.connectwise.com/). This integration provides instructions to integrate ConnectWise Home with IDaaS. Once integrated, users can use single sign-on to log in to their ConnectWise account using IDaaS.](/docs/applications-and-sso/oidc/oidc-and-oauth-integration-guides/integrate-connectwise-home.md)

[📄️ForgeRock You can configure ForgeRock to use IDaaS for multi-factor authentication.](/docs/applications-and-sso/oidc/oidc-and-oauth-integration-guides/integrate-forgerock.md)

[📄️Microsoft Conditional Access Custom Controls Microsoft Entra ID (formerly Azure AD) Conditional Access Custom Controls is being deprecated and will no longer be supported by Microsoft on September 30, 2026. It will be replaced with Microsoft Entra ID. See Integrate Microsoft Entra ID External Authentication Methods. Entrust recommends migrating Custom Controls to External Authentication Methods.](/docs/applications-and-sso/oidc/oidc-and-oauth-integration-guides/integrate-microsoft-conditional-access-custom-controls.md)

[📄️Entra external authentication Microsoft Entra ID is a customer identity and access management (CIAM) solution for managing external identities. See the following documentation for more help:](/docs/applications-and-sso/oidc/oidc-and-oauth-integration-guides/integrate-microsoft-entra-id.md)

[📄️Salesforce You can configure Salesforce to use IDaaS for multi-factor authentication.](/docs/applications-and-sso/oidc/oidc-and-oauth-integration-guides/integrate-salesforce-oidc.md)

info

To create a generic OIDC and OAuth application, see [Integrate OIDC and OAuth cloud applications](/docs/applications-and-sso/manage-applications/integrate-oidc-and-oauth-cloud-applications.md).