docs: note 429 backoff expectations for provider control endpoints
Document that integrations should expect provider-side abuse controls on OAuth control endpoints and handle 429 responses with retry/backoff semantics.
This commit is contained in:
@@ -138,6 +138,7 @@ try {
|
|||||||
|
|
||||||
- Keep provider URLs in environment variables, not hard-coded.
|
- Keep provider URLs in environment variables, not hard-coded.
|
||||||
- Avoid printing tokens in production pages.
|
- Avoid printing tokens in production pages.
|
||||||
|
- Expect `429 Too Many Requests` from provider control endpoints under abuse protection; implement backoff/retry instead of tight loops.
|
||||||
- Rotate client secrets for confidential clients.
|
- Rotate client secrets for confidential clients.
|
||||||
- Add a unique `nonce` to each OIDC authorisation request.
|
- Add a unique `nonce` to each OIDC authorisation request.
|
||||||
- Validate `state` on every callback request.
|
- Validate `state` on every callback request.
|
||||||
|
|||||||
Reference in New Issue
Block a user