Integrations
This section covers the ways external systems connect to Trivore ID: federating sign-in through an external identity provider, keeping other services signed in alongside Trivore ID, customising what OIDC clients receive, exposing permissions to external applications, and letting other services use Trivore ID as their LDAP directory.
In this section
| Page | Description |
|---|---|
| User Directories | Connect external identity providers (LDAP, Azure AD/Entra ID, SAML, Suomi.fi, and others) so users can authenticate through them |
| Distributed Single Sign-On and Single Sign-Out | How SSO and sign-out work across connected services, and how to configure SSO targets |
| Custom OIDC Scopes | Create custom client scopes and mappers to control what data OIDC clients receive |
| External Permissions | Define and grant permissions controlling access to external services and applications |
| LDAP Server | Enable and configure the built-in read-only LDAP server |
| Email Templates | Author the reusable email templates that system messages and other features send |
| Suomi.fi-tunnistus IdP SAML Metadata Change | Update a Suomi.fi-tunnistus user directory's metadata when DVV rotates its certificates |