Skip to content
Public address and redirects

Public address and redirects

For the administrator. Several connections send a person’s browser to a platform and back, and some platforms fetch files from PULSE. Both need the instance’s public address.

Set PULSE_PUBLIC_BASE_URL

Set it on TIDE’s PulseControlPlane resource (or its overlay), never on the live Deployment, to the origin people use to open PULSE, for example https://pulse.example.com, with no trailing path.

It must be https. Over plain http PULSE does not offer Connect with Instagram, YouTube, LinkedIn or Search Console at all, because a sign-in code must never travel in clear text; the cards say what is missing.

The same address is used for:

  • the redirect URIs below;
  • the signed, expiring /media/ links Instagram fetches photos, carousels and videos from (without it the Instagram channel is not ready);
  • absolute links in the podcast feed (/podcast/feed.xml answers 503 without it);
  • the Twilio callbacks (/comms/twilio/inbound, the AI-call routes);
  • a trusted browser origin for the session cookie.

Register the redirect URIs

Redirect URIRegister it inUsed by
<PULSE_PUBLIC_BASE_URL>/oauth/social/callbackthe Meta app, the Google OAuth web client, the LinkedIn appConnect with Instagram, YouTube, LinkedIn
<PULSE_PUBLIC_BASE_URL>/oauth/search-console/callbackthe Google OAuth web clientConnect Search Console
<PULSE_PUBLIC_BASE_URL>/oauth/mail/callbackthe Google OAuth web client, the Microsoft Entra app (Web platform)Connect Gmail, Connect Microsoft 365

Each must match exactly, including https and the absence of a trailing slash. A connect link works once and for ten minutes.

Route them through the TIDE edge

The callbacks are plain HTTP routes on the backend’s one port, like /media/ and /health. The TIDE edge that serves the PULSE host must pass /oauth/social/callback, /oauth/search-console/callback, /oauth/mail/callback, /media/, /podcast/feed.xml and the Twilio paths through to the backend unchanged. If a callback lands on the web app instead, the platform’s sign-in seems to succeed and the card stays not connected. See HTTP endpoints for the full list.