Keycloak and Drupal SSO integration
Signing Drupal users in through Keycloak with the Keycloak OpenID Connect module: client setup, user field and email sync, role mapping changes in the 2.x branch and multilingual login.

Connecting Drupal to identity providers, CRMs, search engines, object storage and API clients through contributed modules documented on Drupal.org.
Signing Drupal users in through Keycloak with the Keycloak OpenID Connect module: client setup, user field and email sync, role mapping changes in the 2.x branch and multilingual login.
Syncing Drupal users, content and form submissions with Salesforce contacts, accounts and opportunities using the Salesforce Suite: field mapping, push and pull timing, JWT authentication and error handling.
Running CiviCRM inside Drupal 10 or 11 for memberships, donations and events: Composer installation, shared or separate database, and exposing CiviCRM data to Drupal views and forms.
Using OpenSearch as the Drupal search backend through Search API OpenSearch: index mapping, facets, More Like This and running the OpenSearch cluster yourself instead of Solr.
Moving Drupal public and private files to Amazon S3 or self-hosted S3-compatible storage such as Ceph with the S3 File System module, for multi-server and container deployments.
Authenticating mobile apps, front ends and partner systems against Drupal with Simple OAuth: supported grants after 6.0, token handling for JSON:API clients and the 5.2 branch end of life.
Signing Drupal users in through Entra ID with the SAML Authentication module or the generic OpenID Connect client, mapping groups to roles, and why the old Azure AD-specific client is not an option on current Drupal.
Connecting Drupal to Okta through the OpenID Connect module's built-in Okta client or SAML, provisioning accounts on first sign-in and role mapping for editors.
Joining campus or research federations through SimpleSAMLphp, a common requirement in higher education: the simplesamlphp_auth module, federation metadata, attribute release and when samlauth is simpler.
Authenticating intranet users against Active Directory or OpenLDAP with the LDAP module: login, provisioning between LDAP and Drupal, group to role mapping and when to move to SAML or OIDC instead.
Sending Webform submissions into HubSpot as leads with the HubSpot module, field mapping, consent capture and the alternative of HubSpot embedded forms.
Replacing Google Analytics with a self-hosted Matomo instance through the Matomo Analytics module, cookie consent implications and data residency benefits.
Adding Google Tag and Tag Manager to Drupal with the Google Tag module, role and path exclusions, and gating tags behind cookie consent.
Connecting Drupal sign-up forms and audiences to Mailchimp, syncing subscriber fields and keeping consent records consistent between the two systems.
Making Drupal mail reliable through an SMTP relay or transactional email service: the SMTP module versus Mailer Plus, HTML templates, SPF and DKIM alignment and testing.
Using Elasticsearch as a Search API backend through Elasticsearch Connector, mapping fields, relevance tuning and the licensing difference that leads some teams to OpenSearch instead.
Indexing the text inside uploaded PDFs and office files with Search API attachments and an extraction service such as Apache Tika, for document libraries and policy portals.
Indexing Drupal content into Algolia through Search API Algolia for hosted instant search, the indexing-only scope of the module and front-end search UI choices.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.