v0.83.0 — catalogue-backed connections and OAuth 2.0
Added
-
ConnectionType::OAuth2for providers that speak OAuth 2.0 and nothing more (GitHub, Discord, Facebook). Kept separate from OIDC because the difference is not configuration: noid_token, no discovery, no signature over the claims.oauth2Config()reads it and refuses a config naming an OIDC provider. -
A
providercolumn on connections, pluscatalogueProvidersFor(). A tenant may enable several catalogue providers at once whileforOrganization()keeps answering "the organization's enterprise sign-on connection". Without the column the first active row won whichever it happened to be — so enabling Google could silently become an organization's SSO.create()refuses a key the catalogue does not have. -
AppleClientSecret— Apple's client secret is an ES256 JWT minted from a downloaded signing key, not a string anyone can paste. Minted on demand, cached for an hour rather than Apple's six-month ceiling, and keyed by the material so rotating a key takes effect immediately. Verified in tests against a real EC public key.
See CHANGELOG.md for the full entry.