Repository navigation
v0.1.0
QAuth v0.1.0 closes the 0.1 line. It is still pre-1.0, and no release has had an external security audit yet; see SECURITY.md.
Security
This release fixes 66 security advisories: 1 critical, 13 high, 37 medium and 15 low.
- 65 come from a private report by Anthropic's OSS Scanner.
- One was found while fixing them.
Every release candidate, v0.1.0-rc.0 to v0.1.0-rc.3, is affected. Upgrade.
The list is in the CHANGELOG and on the advisories page. Each advisory names its fix commits and anything the fix does not cover.
Before you upgrade from v0.1.0-rc.3
- Migrations 0021, 0022 and 0023 run on upgrade.
- Migration 0023 suspends every client that is disabled when it runs.
- An operator lifts a suspension with
db:suspend-oauth-client --lift.
- Authorization errors redirect automatically only to clients an operator provisioned: the system client, or a client from the seed manifest. Every other client gets the error on an issuer page.
REQUIRE_VERIFIED_ACCOUNT, the new name ofREQUIRE_EMAIL_VERIFIED, now defaults totrue.emailscope:- Access tokens carry
emailonly when theemailscope was granted. /oauth/userinfochecks the token's audience.
- Access tokens carry
- Redirect URIs are limited to
https,httpto a loopback host, and reverse-domain private-use schemes. - Wallet sign-in never creates an account.
- The CHANGELOG lists every breaking change and new setting.
Full Changelog: v0.1.0-rc.3...v0.1.0