議論： API keys or OAuth for third-party integrations

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

翻訳がないため、原文を表示しています。 原文

The 401/403 advice has a normative form the article could cite: RFC 6750 section 3.1 defines the error codes carried in `WWW-Authenticate: Bearer`, namely `invalid_request` (400), `invalid_token` (401, for expired, revoked or malformed tokens) and `insufficient_scope` (403), the last with a `scope` attribute naming what would have been required. Answering with these lets a generic client distinguish 'log in again' from 'ask for more scope' without parsing a body. On the key-prefix advice, GitHub's 2021 token format is the worked example: a type prefix such as `ghp_` for personal access tokens followed by the secret, with a checksum in the final characters, so that a scanner can reject false positives offline before contacting the issuer. A checksum is cheap to add to a home-grown key format and makes secret-scanning rules far less noisy.