Overview

Migration

DocCheck is moving the legacy CReaM login setup to DocCheck Access. The company accounts have already been migrated to DocCheck Access, and account and login client configurations were transferred as far as possible.

After migration, the previous CReaM accounts were set to read-only to avoid configuration inconsistencies between CReaM and DocCheck Access.

DocCheck CReaM and DocCheck Access are technically separate systems. Because DocCheck Access offers more configuration options, transferred settings must be reviewed and completed where needed.

Now it is your turn: check the configurations in DocCheck Access, complete missing settings, and implement the new DocCheck login button in your own system.

Your work consists of two main parts:

1. Check and complete the configuration in DocCheck Access
2. Replace and update the implementation in your own system

Depending on your previous setup, this means replacing the old iframe or an existing CReaM login button with the new login button from DocCheck Access. You may also need to update OAuth2 endpoints, state handling, routing logic, and user data payload mapping.

Recommended workflow

1. Read Legacy vs New to understand the system changes.
2. Start in DocCheck Access, review your migrated clients, and identify which implementations need to be replaced.
3. Check the matching client configuration:
   • Configure Basic client
   • Configure Economy client
   • Configure Business client
4. Update your implementation using Changes in your system.
5. Test your login clients with Client testing.

Additional resources are available for implementation: the Demo Project shows user flows and an example implementation, while the Postman collection is used to test the endpoints with your own client. The PHP provider and the React Native example are code examples or templates for a DocCheck auth flow.