From cb0bd43d040a72b0fb7c0d161ed45ae259de56ae Mon Sep 17 00:00:00 2001
From: Andy Dixon <andy@andydixon.com>
Date: Thu, 26 Feb 2026 11:52:41 +0000
Subject: [PATCH] docs: clarify end-user integrations should use OAuth/portal
 endpoints

Add guidance that admin authentication endpoints are scope-restricted and not intended for end-user SDK integrations.
---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 2efe3ac..bdc3d09 100644
--- a/README.md
+++ b/README.md
@@ -131,6 +131,7 @@ This wrapper now delegates to `BlackWall\Auth\AuthClient`.
 - Handle provider callback errors (`error`, `error_description`) explicitly; treat `access_denied` as an expected user/authorisation outcome rather than a transport failure.
 - Expect `access_denied` even after the consent page is displayed if provider-side project membership or tenant scope changes before consent submission.
 - Register only HTTPS redirect URIs in provider client settings (HTTP should be used only for localhost loopback during development).
+- Use OAuth/portal authentication endpoints for end users; provider admin login endpoints enforce separate admin scope checks.
 - For OIDC providers, include a per-request `nonce` in authorisation requests.
 - Always use HTTPS in production.
 - Store refresh tokens securely.