LOW
The issue does not represent a direct security vulnerability but rather an operational challenge. The complexity of managing OAuth tokens for multiple clients can lead to inefficiencies and potential mismanagement errors, but these do not pose immediate threats.

The user is dealing with a complex scenario in n8n, an open-source workflow automation tool, where they must handle OAuth credentials for multiple clients. Each client has their own Gmail and Google Calendar accounts, necessitating the maintenance of separate workflows for each one, which becomes unwieldy as the number of clients grows. The author mentions using an external token store along with an HTTP Request node at the start of a workflow to manage these credentials more efficiently. However, the setup process, including OAuth flow and token refresh infrastructure, is described as cumbersome. This scenario highlights challenges in credential management for multi-tenant environments within automation tools like n8n.

Affected Systems
  • n8n - all versions
Affected Versions: All versions
Remediation
  • Implement an external token store such as Redis or a database to manage OAuth tokens centrally.
  • Create an HTTP Request node in n8n that retrieves the correct OAuth token from your external store based on the client ID at workflow initialization.
  • Update existing workflows to reference this new system for credential handling.
Stack Impact

The impact is primarily on workflows and configuration management within a homelab stack. The setup requires modifications in n8n configurations, including node additions and adjustments to workflow logic.

Source →