FAQ overview
The four categories of the FAQ, how to search by symptom and error code, and how it differs from the error code page.
The FAQ collects questions that have already been asked: confusion from end users facing a consent page, and blockers developers hit during integration. It is not systematic by design — it aims at "follow this and it is fixed".
This page explains how to use the section and how it relates to the error code page.
Four categories
| Reader | What they care about | Category |
|---|---|---|
| End users | Passwords, verification methods, sessions, someone else using my account | Account and security |
| End users | Why sign in again, why verify once more | Sign-in and verification |
| End users and developers | What the consent page asks, what revoking does, scopes and audiences | Authorization and permissions |
| Developers | Why this error, why a scope is missing, whether a secret can live in the frontend | Integration and debugging |
User-side answers assume no terminology at all; developer-side answers assume you know what a client_id is. Start from the FAQ overview if you are unsure which category fits.
How to search
Try in this order, each step narrower than the last:
- By symptom: the thing you see (no consent page, a 404 on the callback, a 401 on a token) maps directly to an entry;
- By error code: Error codes gives the troubleshooting order; the FAQ gives the conclusion;
- By field: API reference gives parameters and constraints.
How it differs from the error code page
| Page | Question it answers |
|---|---|
| Error codes | What is the basis for this error code, and in what order do I investigate |
| FAQ | In this scenario, what is it usually, and how do I fix it |
The error code page is complete and organised by protocol; the FAQ is empirical and organised by scenario. When they disagree, the error code page wins.
Categories at a glance
Each category has its own overview page listing the questions it answers and stating what deliberately does not belong there:
- Account and security — passwords, verification methods, sessions, devices;
- Sign-in and verification — sessions, re-authentication, step-up;
- Authorization and permissions — scopes, audiences, revoking access;
- Integration and debugging — clients, callbacks, token exchange, local testing.
When nothing matches
Report it as "the docs are wrong" rather than working around it: a workaround leaves a long-term hazard, a wrong doc gets fixed. Change notes and feedback conventions are in the documentation outline.