Can customers connect their own identity providers?
Yes. amaise supports connecting customer-specific identity providers. Microsoft Entra ID and OpenID Connect (OIDC) are the default and recommended protocols; SAML 2.0 is available on request:
Microsoft Entra ID (default, recommended) — native OIDC integration with group-to-role mapping and automatic user attribute synchronization at each login
Generic OpenID Connect (OIDC) — back-channel OIDC with configurable issuer, JWKS, and token/authorization endpoints, for example when users are keyed on a custom attribute such as an internal employee number
SAML 2.0 (on request) — for identity providers that use SAML; on-premise Active Directory directories are connected via AD FS (Active Directory Federation Services)
Each SSO customer receives a dedicated organization in the authentication service with individual branding (logo, colors, login page). The customer's IdP groups are mapped to amaise tenants and roles via metadata-based configuration.
Automated provisioning: By default, users are created and updated just-in-time at each login. SCIM-based automatic provisioning is available on request — not by default.