This project is not covered by Drupal’s security advisory policy.

Connector Hub Google adds "Sign in with Google" and Google Calendar to Connector Hub, using a shared OAuth2 layer, so a visitor can register with their Google account or a site can manage calendar events.

Introduction:
Connector Hub Google is an integration module built on Connector Hub and its authentication add-on, Connector Hub Auth. It connects your site to Google in two ways out of the box: letting visitors sign in or register using their Google account, and letting your site create and read events on a connected Google Calendar. Both use Google's own OAuth2 sign-in screen, so no password is ever handled or stored by your site.

Features

- "Sign in with Google": visitors register or log in with their Google account through a placeable block and a dedicated route. A new Drupal account is created automatically on first sign-in and recognized on every sign-in after that.
- Google Calendar: your site can create and list events on a connected Google Calendar, using a standing connection set up once by an administrator.
- Each Google feature only asks for the narrowest Google permission (scope) it actually needs, never broad account access.
- Built on a shared, reusable OAuth2 layer (Connector Hub Auth), so future Google integrations (such as Gmail or Google Sheets) can be added as new, independent pieces without touching what is already there.
- Use "Sign in with Google" when you want a lower-friction registration and login option on your site. Use the Calendar feature when your site itself (not a visitor) needs to create or check events, such as booking confirmations or availability.

Post-Installation

This module provides no functionality by itself; enable the piece you actually need:
- For "Sign in with Google", also enable Connector Hub Google: Sign in with Google. Create a connection under Configuration > Web services > Connector Hub using the "Google sign-in" plugin, with your Google OAuth client ID and a Key holding the client secret, then place the "Sign in with Google" block wherever visitors should see it.
- For Calendar access, also enable Connector Hub Google: Calendar. Create a connection using the "Google Calendar" plugin, then use the "Connect" action that appears on its settings page to grant access through Google's own consent screen.

Both features require a Google Cloud project with an OAuth client, created once by the site owner in Google's own developer console.

Additional Requirements

- Requires Connector Hub and Connector Hub Auth, which provide the underlying connection framework and the OAuth2 mechanics.
- Requires the Key module, used to store the OAuth client secret.
- The "Sign in with Google" piece additionally requires the Externalauth module, used to link a Google account to a Drupal user.
- Requires a Google Cloud project with an OAuth 2.0 client, set up by the site owner outside of Drupal.

- Connector Hub and Connector Hub Auth (required).
- Externalauth (required for the sign-in feature only).

Similar projects

Other modules offer "Sign in with Google" on their own, outside of any connection framework. This module's sign-in feature is deliberately built on the same connection and authentication layer as every other Connector Hub integration, so a site already using Connector Hub for something else (such as payments) reuses the same admin screens and the same underlying OAuth2 code, rather than adding a second, unrelated way of handling Google credentials.

Supporting this Module

No sponsorship links at this time.

Community Documentation

A full developer reference, including how the login and calendar features are built on Connector Hub Auth, lives at [connector-hub.porschmann.be/docs.html](https://connector-hub.porschmann.be/docs.html).

Project information

  • caution Seeking co-maintainer(s)
    Maintainers are looking for help reviewing issues.
  • Project categories: Developer tools, Integrations
  • Created by mookum on , updated
  • shield alertThis project is not covered by the security advisory policy.
    Use at your own risk! It may have publicly disclosed vulnerabilities.

Releases