Glossary

WWW-Authenticate header

A 401 response header that tells a client how to authenticate and where to find the sign-in server.

Updated November 12, 2026

Standard
RFC 9110

At OneLifeVibe

Related terms

What it means

The WWW-Authenticate header is the response header a server sends with a 401 to tell the client how to authenticate and where to find the sign-in server. It is defined in RFC 9110. A 401 means the request did not carry valid credentials for the resource. The header is the instruction for fixing that: it names the authentication scheme and can carry parameters that point the client somewhere useful.

A bare 401 leaves a client guessing. With the header attached, the failure becomes a machine-readable next step. The client reads it, finds the authorization server, gets a token, and tries the request again.

How it works

The header value starts with an auth scheme, such as Bearer, followed by comma-separated parameters. In OAuth flows the useful parameter points at the protected resource metadata document. That document states which authorization server covers the resource, so the client knows who to ask for a token.

The usual exchange looks like this. A client calls a protected endpoint with no token. The server replies 401 with WWW-Authenticate. The client fetches the metadata URL from that header, runs the OAuth flow, then retries the original request with Authorization: Bearer <access token>. Discovery comes from the server's response, so the client does not need the sign-in URL compiled in ahead of time.

How OneLifeVibe uses it

The OneLifeVibe MCP server, the assistant connector, requires Authorization: Bearer <access token> on every MCP request. Send one without it and the server answers 401 with a WWW-Authenticate header pointing at the protected resource metadata.

That metadata is served at https://onelifevibe.com/.well-known/oauth-protected-resource/mcp and at https://onelifevibe.com/.well-known/oauth-protected-resource. A 401 from /mcp carries the header pointing at it. This is how MCP clients discover where to sign in: read the header, fetch the metadata, then complete sign-in with the OneLifeVibe account.

Common mistakes

Treating the 401 as a dead end. For the OneLifeVibe MCP server it is the discovery step, not an error to show the user and stop on.

Hardcoding the metadata URL and ignoring the header works right up until the advertised location changes, so read what the server sends. Another common slip is dropping the Bearer prefix or the space after it, which gives you a token the server will not accept.

Questions

Why does my MCP request return 401?

The request is missing Authorization: Bearer <access token>. The /mcp endpoint responds with 401 and a WWW-Authenticate header pointing at the protected resource metadata, which is where you go to sign in and get a token.

Where does the WWW-Authenticate header point on OneLifeVibe?

It points at the OAuth protected resource metadata served at https://onelifevibe.com/.well-known/oauth-protected-resource/mcp, also available at https://onelifevibe.com/.well-known/oauth-protected-resource. That document tells the client where to sign in.

See it working. The OneLifeVibe connector and Platform API put these pieces together.

Get a free key Read the docs

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.