Workspace Auth Headers

Signed-in visitors receive both oai-authenticated-user-id and oai-authenticated-user-email. Private Sites require every visitor to sign in; public Sites may also have anonymous visitors, for whom neither header is present.

The user ID is stable for the same user on the same Site and different across Sites. Use it as the durable user key; use email and name for display or contact purposes.

SIWC-authenticated workspace sites may also receive oai-authenticated-user-full-name when the user's SIWC profile has a non-empty name claim. The full-name value is percent-encoded UTF-8 and is accompanied by oai-authenticated-user-full-name-encoding: percent-encoded-utf-8.

Treat the full name as optional and fall back to email when it is absent:

1import { headers } from "next/headers";
2 
3export default async function Home() {
4  const requestHeaders = await headers();
5  const userId = requestHeaders.get("oai-authenticated-user-id");
6  const email = requestHeaders.get("oai-authenticated-user-email");
7  const encodedFullName = requestHeaders.get("oai-authenticated-user-full-name");
8  const fullName =
9    encodedFullName &&
10    requestHeaders.get("oai-authenticated-user-full-name-encoding") ===
11      "percent-encoded-utf-8"
12      ? decodeURIComponent(encodedFullName)
13      : null;
14 
15  const displayName = fullName ?? email;
16  // ...
17}