NLWeb Auth & Multitenancy

Before writing code

Fetch live docs:

1. Fetch https://github.com/nlweb-ai/NLWeb/blob/main/docs/setup-oauth.md for OAuth configuration.
2. Fetch https://github.com/nlweb-ai/NLWeb/blob/main/docs/nlweb-memory.md for conversation persistence.
3. Inspect AskAgent/python/webserver/routes/oauth.py for the current OAuth flow.
4. Inspect AskAgent/python/core/conversation_history.py and storage_providers/ for persistence backends.
5. Check config/config_oauth.yaml and config/config_storage.yaml for current keys.

Conceptual Architecture

NLWeb's Auth Model — What It Does and Doesn't Do

NLWeb ships OAuth-based user identification — it lets a logged-in user have persistent conversation memory tied to their identity. It does not ship:

• Fine-grained authorization (per-site ACLs)
• API key auth for service-to-service callers
• Multi-tenant data isolation at the retrieval layer