Service

Integrations and single sign-on

Connecting Drupal to the systems of record — SAML, CAS and LDAP identity, student information systems, CRMs, payments and reporting.

What you get

  • SAML, CAS, LDAP or OAuth authentication
  • Per-environment key and metadata management
  • User provisioning and role mapping
  • System-of-record integrations
  • Payment gateway integration
  • Dashboard and reporting embeds

Integration work is where a project meets the parts of an organisation it does not control, and the failure mode is always the same: it worked in staging.

So identity integrations are built per environment from the start — separate keypairs, separate metadata, separate secrets in the platform's secret store — and account migration is planned before cutover rather than discovered during it. We have moved sites between SSO implementations, matched existing accounts to new identity providers, and patched authentication contexts to satisfy an institution's requirements.

Questions we get asked

It blocks the integration, not the build. The work is sequenced so everything else proceeds, and the SSO piece is stubbed locally against test metadata until the real thing is available.