Authentication
The Authentication section of Administration controls how people and machines get in to Informer: API Tokens for scripts and integrations, OAuth Client Apps and Integrations for connecting external services, sign-in Domains (Active Directory, LDAP, and SAML single sign-on), and the active Sessions on the system.
In this section
| Article | In one line |
|---|---|
| API Tokens | Create, copy, and manage the Tokens that authenticate API access. |
| Connecting to Informer via OAuth Client Apps | Let external applications connect to Informer as a service provider. |
| Adding a Domain | Authenticate Users against Active Directory or LDAP. |
| Configuring a SAML Domain | Set up SAML single sign-on between Informer and an identity provider. |
| Configuring a SAML Domain with an Entra Identity Provider | Map a Microsoft Entra (Azure) enterprise application to an Informer SAML Domain. |
| Configuring a SAML Domain with an ADFS Identity Provider | Map a Microsoft ADFS Relying Party Trust to an Informer SAML Domain. |
| Adding Users from a Domain | Scan an AD or LDAP Domain to create Users and Teams in bulk. |
| Updating a User's Authentication Domain to SAML | Migrate existing Users from Local, AD, or LDAP onto a SAML Domain. |
| Integrations | Connect Informer to external services via OAuth as the client. |
| Client ID and Client Secret for Google Drive Libraries | Create Google Cloud OAuth credentials for a Google Drive Library. |
| Client ID and Client Secret for Box Libraries | Register a Box app for a Box Library. |
| Client ID and Client Secret for GitHub Libraries | Register a GitHub OAuth app for a GitHub Library. |
| Client ID and Client Secret for Microsoft OneDrive Libraries | Register an Azure app for a OneDrive Library (2025.1.x and earlier). |
| Sessions | View, filter, and terminate active login sessions. |