Implement Single Sign-On (SSO) for Autoform DM

Autoform DM can integrate into a single sign-on (SSO) environment. The main benefit is that a trusted identity provider (IdP) handles user authentication and the management of the user identities and group memberships that control access to Autoform DM and its applications.

Also, this capability enables a seamless integration of the sign-on experience of Autoform DM and other applications and services within the same security domain.

This feature currently supports integration with Microsoft Entra ID.

This guide describes what this SSO feature supports, how to implement it, and provides steps that describe how to enable and configure it.

Note

After Autoform DM single sign-on is enabled, external applications and services (such as Lasernet, other Formpipe applications, and third-party applications) must use OAuth2 to authenticate. They cannot continue to use API keys or credentials to authenticate with Autoform DM.

For more information, see Integrate Applications and Services (Lasernet, Other Formpipe Applications, and Third-Party Applications) with Autoform DM.

Next Steps

For information about the implementation process for Autoform DM SSO, see the following relevant page:

• Implementation Process for Formpipe Cloud Customers

• Implementation Process for Customers Using a Self-Hosted Cloud or On-Premises System

Intended Audience

For all of this guide’s audiences, an understanding of single sign-on and its underlying concepts and flows is assumed.

Formpipe Cloud Customers

For Formpipe Cloud customers, the intended audience is the engineers (at the customer organization) who are responsible for administrating the customer organization’s identity infrastructure. Their role in this implementation process is to make specific necessary changes in that infrastructure and then supply relevant information to Formpipe (so that we can complete the rest of the process within Formpipe Cloud).

Customers Using a Self-Hosted Cloud or On-Premises System

If a customer is running Autoform DM in a self-hosted cloud environment or as an on-premises system, the entire implementation process must be completed by their engineers (or engineers from the Formpipe partner organization that is implementing Autoform DM for them).

As a result, the intended audience is any engineer in the customer or partner organization who has a role in the implementation process.

Formpipe Staff

Formpipe staff can be involved in implementing Autoform DM SSO for customers using a self-hosted cloud or on-premises Autoform DM system.

As a result, the audience for this guide includes any Formpipe staff member who might be involved at any stage of the SSO implementation process.

Scope

The scope of the documented process covers Microsoft infrastructure (Azure and Entra ID) and Keycloak only.