16 docs tagged with "saml-sso"

Understand how user accounts are organized in cidaas.

OAuth2/OIDC application types (client_type values), recommended flows, and configuration availability by type in cidaas.

cidaas can act as an OpenID Connect (OIDC) Identity Provider (IdP) for external applications.

Claim consent in cidaas — let users authorise the release of identity claims such as name, email or roles to an application before a token is issued.

Identity providers in cidaas — connect SAML, OAuth 2.0, OpenID Connect, and LDAP/AD for enterprise and social SSO.

cidaas supports LDAP (Lightweight Directory Access Protocol) and Active Directory for authentication and user synchronization. You can configure cidaas to act as an Identity Provider (IdP) or as a Service Provider (SP).

The cidaas login hosted page — learn how to set it up, add login providers, and connect the login success page that follows a successful sign-in.

cidaas supports OAuth2 and OpenID Connect (OIDC) for Single Sign-On (SSO) authentication. You can configure cidaas to act as an Identity Provider (IdP) or as a Service Provider (SP).

Learn how to implement self-service user registration in cidaas, including webfinger user existence checks, invitation-based registration, and the complete registration flow.

Remote Fields is an advanced feature in cidaas that allows field values to be dynamically fetched from an external API during token generation or user profile retrieval.

SAML 2.0 Single Sign-On in cidaas as Service Provider — configure external IdPs, assertions, attributes, and logout.

Configure cidaas as a SAML 2.0 Identity Provider — register an external SP with the SAML_SP app type in Trustdesk.

Session management lets users stay signed in across applications and devices. This guide explains how sessions relate to OAuth 2.0 and OpenID Connect in cidaas, and points you to the right flows for validation, logout, and native-to-web handoff.

Native applications (for example mobile apps) often open company-owned web applications in the system browser: centralized profiles, webshops, help portals, and similar. Those sites typically expect an active IdP session in the browser—the same kind of session that powers Single Sign-On (SSO) for pure web apps—not only a token inside the native app.

Validate cidaas tokens — check authenticity, expiry and audience of access, ID and refresh tokens, with a practical validation checklist.

Domain- and user-based redirection in cidaas — use webfinger to send users straight to their own identity provider, bring-your-own-identity style.