Unify Logo Footer.svg
Unify Automations
Logo
Manage Identity Providers

Manage Identity Providers

Logo

3 mins READ

The Auth node's identity provider operations let you configure how users sign in — from standard password logins to SAML, OIDC, LDAP, biometric, external sessions, and custom workflows. The platform can also act as a SAML identity provider itself, issuing signed assertions for external service providers.

Overview

An identity provider (IdP) is the configuration record that defines one sign-in method for your application. The Auth node lets you create, update, delete, and fetch identity providers programmatically — managing them as part of an automation rather than only through the platform's settings UI. Multiple providers can coexist; route users to the right one by its identifier in your login automation. An additional operation, Generate SAML Response, lets the platform issue a signed SAML assertion so that external service providers can authenticate users through UnifyApps.

Operations

Create Identity Provider

Adds a new identity provider configuration. Choose one of the supported types: SAMLOpenID Connect (OIDC)passwordLDAPbiometricexternal session, or custom workflow. Each type has its own configuration fields appropriate to that sign-in method.

Update Identity Provider

Modifies an existing identity provider's configuration by its identifier. Use this to rotate credentials, update endpoint URLs, or change the provider's settings without deleting and recreating the record.

Delete Identity Provider

Removes an identity provider configuration permanently. Existing sessions created with this provider are not automatically invalidated — plan session cleanup separately if you need to force all users off a deleted provider.

Fetch Identity Provider

Retrieves the configuration of a specific provider by its identifier. Use this to confirm current settings or to read the provider's ID for use in downstream steps.

Generate SAML Response

Produces a signed SAML assertion for a service provider. Use this operation when UnifyApps acts as the identity provider in a SAML integration — other applications sign in through the platform rather than directly. Configure the target service provider's details and the assertion's attributes before calling this operation.

Notes

Keep the following in mind when managing identity providers through automation.

  • Supported provider types: SAML, OIDC, password, LDAP, biometric, external session, and custom workflow.

  • Route login requests to the correct provider by its identifier — each IdP has a distinct ID that your login automation uses to direct the request.

  • Generate SAML Response makes the platform act as a SAML IdP; use it only when external service providers are configured to trust UnifyApps assertions.

  • A provider can be configured to require different MFA factors for different actions — for example, an authenticator app for login and an emailed code for password reset.

  • Deleting a provider does not expire sessions previously issued under it; plan explicit session deletion if you need to force re-authentication after a provider is removed.

When building SSO integrations, confirm that the SAML or OIDC metadata exchanged between UnifyApps and the service provider is current and matches your production configuration before going live.

FAQs

What is a custom workflow provider?

A custom workflow provider lets you define your own sign-in logic beyond the standard built-in types. Use it when none of SAML, OIDC, password, LDAP, biometric, or external session matches your environment's authentication approach.

What is an external session provider?

An external session provider bridges a login from another system. A user who is already authenticated in an outside application is admitted through this provider type, which translates the external session into a platform session.

Can I use more than one identity provider in the same application?

Yes. You configure multiple providers, each with its own type and settings, and route users to the appropriate one by its identifier in your login automation.