Skip to main content
Version: Latest (4.0.2)

Integration Checklist

Use this checklist in customer kickoffs and discovery workshops. It lists the topics to clarify and plan before implementation. It is intentionally high-level — detail lives in the linked guides.

How to use

Walk through each section with stakeholders (business, IT, security, support). Mark what applies, capture decisions, and assign owners. Skip sections that are out of scope for the first release.

1. Scope and stakeholders​

Clarify why you integrate cidaas and who is involved.

  • Primary use cases (SSO, registration/login, B2C, B2B, employee access, …)
  • Applications and channels in scope for the first go-live
  • Success criteria and timeline / phases
  • Roles and owners (business, architecture, development, security, support, legal)

→ Related: Integrate cidaas into your business, Integration Roadmap

2. Identity model​

Define what a user is in cidaas and how access is structured.

  • Login identifier(s) (email, mobile, username / business ID)
  • User attributes and custom fields (what belongs in cidaas vs. CRM / other systems)
  • Groups, roles, and permissions concept
  • How apps enforce authorization (token claims, APIs, group/role restrictions)

→ Related: Permissions and Group Concept, Group Role Restrictions, Instance Setup — Fields

3. Authentication and user experience​

Decide how users sign in and what the journey looks like.

  • Hosted pages (default / themed) vs. custom hosted pages
  • Branding, languages, and communication templates (email / SMS)
  • Custom domain
  • Authentication methods (password, passwordless, social / external IdPs)
  • Password policy (if passwords are used)
  • Profile / self-service page requirements

→ Related: Hosted Page Decisions, Custom Domain, Profile Page, Instance Setup

4. Verification, consents, and compliance​

Cover security and regulatory requirements early.

  • Verification / MFA methods per use case or risk level
  • Consent types and when they are collected (registration, profile, marketing)
  • Legal / privacy review of flows and data stored in cidaas
  • Support impersonation needs (if applicable)

→ Related: Consents, Email and Mobile Number, Impersonation, Instance Setup — Consents & Verification

5. Applications and clients​

Inventory every app that will talk to cidaas.

  • Application inventory (web, SPA, native/mobile, backend, third-party)
  • Protocol per app (OIDC/OAuth2, SAML as IdP and/or SP, plugin / DevKit)
  • Redirect URIs, environments (dev / test / prod), and client configuration
  • Native / mobile specifics (no webviews for login, token handling)
  • Ready-made plugins where applicable (Shopware, WordPress, TYPO3, …)

→ Related: Instance Setup — Client Applications, SAML (IdP and SP), Native Clients, Native App Cutover, Plugins

6. System landscape​

Plan how cidaas connects to the rest of the landscape. Ownership is situational — decide per attribute which system is authoritative (see External Systems Integration). After a completed cutover, many projects treat cidaas as the identity master; during bidirectional migration both IdPs may be co-sources until the last app moves.

  • CRM / business systems (link via sub, event sync)
  • Marketing / communication tools (templates, consents, providers)
  • Reporting / analytics needs
  • Integration pattern (webhooks, APIs, batch, SCIM)
  • Backend token validation and API security

→ Related: External Systems Integration, SCIM Provisioning, Integrate cidaas into your business, Integration Roadmap, Backoffice and Support

7. Data migration (if replacing a legacy IdP)​

Only if users, passwords, or related identity data already exist elsewhere.

  • Source systems and volume
  • Merge / deduplication strategy
  • Password / credential migration approach
  • Refresh token migration (keep users signed in after cutover, if applicable)
  • One-time vs. sync / bidirectional migration
  • Cutover and rollback expectations

→ Related: Migration Overview, Migration Planning, Password Migration, Refresh token migration

8. Go-live and operations​

Plan how you launch and run the solution.

  • Test strategy (staging, key user journeys per app)
  • Go-live order per application
  • Support / backoffice processes and access
  • Monitoring, webhooks, and incident ownership
  • Documentation and training for ops / support

→ Related: Go-Live Checklist per Application, Instance Setup Checklist, Backoffice and Support

Next steps​

After the kickoff:

  1. Turn open decisions into a short decision log (owner + due date).
  2. Configure the instance using the Instance Setup Guide.
  3. Implement app and system integrations using the guides linked above.
  4. If migrating users, follow the Migration Planning Guide.