Skip to main content

Integration Guides

Business, Mobile and Web Apps​

The most common use case for cidaas is to provide single sign on. Login once and grant access to different applications. cidaas is based on the OAuth2 and OIDC standards, which provide an easy and secure way to integrate it in your business applications. No OAuth/OIDC - no problem: we also support SAML or find a custom solution with you.

Login and registration are handled on centralized pages to separate user credentials from business applications. These pages could be specific to an app, channel or can be designed uniformly to strengthen high recognition and the feeling of familiarity. Changes in login or registration process can appear in every application very fast and with less effort.

Benefits:

  • Single sign on - SSO
  • Unified login and registration mechanism
  • Separate user credentials from business logic
  • Adapt login & registration flows quickly and easily
  • Group and role restrictions

Application specific Backends​

One target of the integration of cidaas should be to build up a centralized master user identity, which will be used by all your applications. However, there could be cases with legacy systems or architectural reasons, where we need to share user data with application backends. In that case cidaas should always be master, updates in applications must also be sent to cidaas.

Benefits:

  • Link identity to application data
  • Share identity data to further systems
  • Support legacy systems

Customer Relationship Management​

Order history, payment data or extended product specific user data are stored in a CRM system and shouldn't be stored in cidaas. cidaas creates a unique identifier (sub) for each account. The sub should be linked to the identity in CRM.

cidaas sends different events like user create, user update and user delete to notify the CRM for updates.

Benefits:

  • Link identity to business data (order data)
  • Separate user data and personalized business data

Marketing Tools​

cidaas sends emails by default via a system provider. Templates, sender configuration (like sender name) and volume can be configured. Nevertheless, it could make sense to reuse existing tools to have centralized email templates - registration/login related, newsletter or other marketing emails.

Benefits:

  • Send emails and SMS through your known and familiar marketing tool
  • Manage newsletter consents during registration or in user profile

Reporting Tools​

Number of users, number of logins or number of registrations are helpful reports for multiple departments in your company, e.g. to measure the success of a marketing campaign. cidaas provides those reports and will expand report functionalities in future. We get some requests for custom specific reports which are not part of the product. To cover all of them cidaas provides around 100 different webhook events, which can send information to your reporting tool to generate your own reports.

Benefits:

  • Real-time reporting
  • Customer specific, independent reporting

Integration Best Practices​

Once you've completed user migration (or if you're starting fresh), explore these integration guides:

System Integration - External systems, profile pages, and support tools
Core Configuration - Hosted pages, domains, permissions, and consents
Client-Specific Integration - Mobile apps, email/SMS, and impersonation
Ready-to-Use Plugins - Pre-built integrations for popular platforms

login page