Technology and integration

Identities in Keycloak.

Applications sign in via SAML 2.0 or OpenID Connect, mailboxes in OX are created through the API, and older applications get custom interfaces. The regional associations’ membership databases are synchronised continuously.

Architecture

Sources, identity management, applications.

The membership databases supply each person’s unit and role. Identity management derives the permissions from them and provides sign-in and application roles to all connected applications.

Sources

Membership databases

  • Regional association A, system 1
  • Regional association B, system 2
  • Regional association C, system 3
  • CSV files for units without an interface

Continuous synchronisation. Changes made in self-service flow back.

Connecteeva

Identity management

on Keycloak

  • People with unit and roles
  • Structure from national association to local branch
  • Rules: role determines permissions
  • Two-factor authentication
  • Administration per level and self-service
  • Audit log of all changes

Applications

Sign-in and permissions

SAML 2.0 and OpenID Connect

  • Chat, video, file storage, wiki, learning platform
  • Web applications with standard integration

OX API

  • Email, calendar and contacts in OX App Suite

Custom interface

  • Older specialist applications, your own member app

Sign-in and claims

Sign-in via SAML and OpenID Connect.

Applications that support SAML 2.0 or OpenID Connect are connected without programming. This covers most web applications, learning platforms, wikis and forums.

People sign in everywhere with the same credentials. At sign-in, the application learns which unit the person belongs to and which roles and application roles they hold.

The application uses the application roles to decide whether the person has read access or further permissions. A separate user list and separate passwords in the application are no longer needed.

When a person’s role changes, the application receives the new application roles at the next sign-in.

SAML 2.0OpenID ConnectOAuth 2.0LDAP and Active Directory

Identifier

Unique, persistent identifier of the person

Name and email

Name and email address from the identity

Unit

Position in the tree e.g. national association, North regional association, Nordstadt district branch, Lindenhof local branch

Roles

Roles in the unit e.g. local branch chair, treasurer, member

Application roles

Permissions in this application, derived from the association’s rules e.g. read, edit, manage

Which details an application receives is set per application. Each application gets only what it needs for its task.

Accounts in applications

If an application needs its own accounts, Connecteeva creates them.

For sign-in, the standard protocols are enough for most applications.

OX App Suite via the API

Email, calendar and contacts

  • When the service is assigned, the mailbox is created in OX, with address, aliases, storage and feature set.
  • When the identity or the assignment changes, Connecteeva updates the account in OX.
  • When the identity ends or the service is withdrawn, Connecteeva removes the account.
  • Additional domains can be run in the same OX context.

Custom interfaces

Applications without standard integration

  • For older specialist applications or your own member app, we build interfaces as needed and extend them.
  • These applications also receive unit, roles and application roles from identity management.
  • Accounts in the application are created and closed with the identity, as with OX.

Membership databases

Each membership database is connected individually and mapped to a common model of person, unit and role.

What is imported

Joiners, leavers, moves to another local branch and changes of role. Accounts are created, changed or locked without anyone stepping in.

What flows back

If a member changes their email address in self-service, the change can be passed back to the membership database.

Without an interface

For the initial setup and for units without a connected membership database, people are added by CSV import.

Your own applications

What your association develops itself uses the same sign-in.

Sign-in via OpenID Connect

A web application or member app signs in its users via OpenID Connect. Ready-made libraries are available for the common programming languages.

Permissions from application roles

The application checks the application roles it receives instead of maintaining its own permissions. Whoever takes on a role in the association has the matching permissions in your own application too.

Development by us

If you wish, we develop the integration or the whole application. We also develop Connecteeva’s administration interface and portal ourselves.

Security

Two factors, stricter rules for administrator accounts.

Two-factor authentication

As you specify: for everyone, by role or optional. People set up the second factor themselves and manage their devices.

Administrator accounts

Stricter rules for accounts with administrative permissions or access to member data, if you choose.

Visibility

Administrative permissions apply to a unit and everything below it. Neighbouring and higher levels are not visible.

Locking

Immediate locking of all access when a person leaves or an account is compromised.

Audit log

All sign-ins and administrative actions with person and time. The audit log cannot be altered through the interface.

Recent sign-ins

An overview shows unused accounts.

Passwords

People reset their own password in self-service. The responsible unit can set a temporary password.

Transport

Encrypted.

Operations

Run by czichos.net GmbH.

Identity management holds memberships, roles and permissions, and in social welfare associations also information about people’s circumstances. Whoever runs it controls access to every service.

Operator

czichos.net GmbH, Berlin, without a US parent company. The US CLOUD Act does not apply.

Data centres

In Germany, your choice of Hetzner, ScaleUp Technologies or, on request, a data centre in Berlin. The location affects the price.

US hyperscalers

No service runs on Amazon Web Services, Microsoft Azure or Google Cloud.

Environment

A shared environment with each organisation kept separate, or a dedicated environment on request from 50 accounts.

Software

Identities in Keycloak, services on open-source software. czichos.net GmbH develops the administration interface and portal itself.

Monitoring

Checkmk with real sign-in and access tests, queues, certificates and capacity. A status page for your services is included at no extra cost.

Availability

99.9% as an annual average, excluding announced maintenance windows, for the services that czichos.net GmbH runs for you.

Backup

The Connecteeva system is backed up daily, mailboxes every 15 minutes as snapshots. The backups are stored geo-redundantly at physically separate locations, and we agree with you how long they are kept. We regularly test that data can be restored. The backups are set out in the data processing agreement.

Versions

A new version about every two weeks. The changes are listed in the public changelog.

Support

By email, usually on working days from 8am to 4pm, with a call back if you prefer. Technical support is included. Existing customers have an emergency hotline around the clock.

Documents

Data processing agreement under Art. 28 GDPR, technical and organisational measures, list of subprocessors and the data centre operator’s ISO/IEC 27001 certificate, on request.

Export

Identities, structure and permissions can be exported at any time.

Identities and structure

People with unit, roles and permissions, and the tree of units, can be exported. Each unit exports filtered user lists for its area.

Open standards

The identities are held in Keycloak, which is open-source software. Applications are connected via SAML or OpenID Connect and can be switched to another sign-in service.

When the contract ends

Export of mailboxes, calendars, contacts and files. The data is kept for at least 30 days after the contract ends. Your domain belongs to you.

Introduction

Introduced in stages. Existing systems keep running.

Identity management grows with each connected membership database and application. Your association decides the order and the pace.

  1. Describe structure and rules Together we describe the levels, the groups of people and the rules by which roles become permissions.
  2. Connect the first membership database One regional association starts. The synchronisation is tested and adjusted with its real data.
  3. Connect the first application A service with a clear benefit goes live first, such as email for volunteers or the digital member magazine.
  4. Add further regional associations Each further membership database is mapped to the common model.
  5. Connect further applications Existing and new applications are added step by step. An application is only switched over once its integration has been tested.

Clear up your technical questions with us. We usually reply within one working day.

Tell us which applications and membership databases should be connected and which protocols they support. We reply in writing or arrange a meeting with your IT.

We set up trial access and usually send the login details to your contact email within one working day.

No contract and no payment details.

Prefer to reach us directly? Send an email · call +49 30 994048000

Address czichos.net GmbH
Königsweg 220
14129 Berlin, Germany