Authentication
Compose credentials, magic links, sessions, passkeys, MFA, and connected-provider access without handing application identity to a framework.
Auth.js provider sign-in
Auth.js
Bridge Auth.js provider callbacks into Playstack identity and session contracts while retaining application-owned provider configuration.
Visit Auth.js ↗Supported features
Package reference
Provider sign-in at the edge
Auth.js owns provider protocol and callback orchestration. The Playstack bridge translates successful provider identity into portable credential and session behavior.
Normalize the Auth.js profile explicitly, then call
CredentialService.authenticateProfile(). Playstack applies the same
verified-email linking, reservations, transaction, and identity events used by
its provider-owned authorization-code path. The bridge projects only the narrow
Playstack session view into Auth.js’s encrypted JWT and works with both Next.js
routers.
Provider definitions, secrets, route placement, and Auth.js module augmentation remain application-owned.
