Standards
The specifications php-sso implements, and what it does for each.
| Specification | What php-sso does |
|---|---|
| OpenID Connect Core 1.0 | Authorization code flow, ID tokens with nonce, auth_time and amr, UserInfo, prompt=login, prompt=none and max_age. |
| OpenID Connect Discovery and RFC 8414 | One discovery document, served at both well-known addresses, with the signing keys in a JWKS. |
| OAuth 2.0 (RFC 6749) | Authorization code, refresh token and client credentials grants. There is no password grant and no implicit flow. |
| PKCE (RFC 7636) | S256 is required for every app. plain is refused. |
| RFC 9068 and RFC 9207 | Access tokens are signed JWTs of type at+jwt. Authorization responses carry the issuer, so an app can tell servers apart. |
| Device grant (RFC 8628) | A TV or command line shows a short code, and the person approves it on their phone. Wrong codes are limited. |
| Revocation and introspection (RFC 7009, 7662) | Both endpoints, with introspection limited to confidential apps such as APIs. |
| RP-initiated and back-channel logout | Signing out of one app ends the session, revokes its tokens and tells the other apps that support it. |
RFC 8176 (amr) | Says how someone signed in: pwd, otp, mfa, or fed for an outside account. |
| TOTP (RFC 6238) | Six-digit codes every 30 seconds from any authenticator app. A code works once. |
| QR Code (ISO/IEC 18004) | The code you scan to set up two-step verification is drawn by php-sso itself, so the secret never goes to an outside service. |
| SAML 2.0 | php-sso is the service provider. Web SSO with a redirect out and a signed POST back, in the php-sso/saml package, which uses the onelogin/php-saml library. |
| SCIM 2.0 (RFC 7643, 7644) | Users and groups: create, read, look up with eq filters, replace, patch and delete. No bulk, sorting or ETags. |