Context
We're adding Google OAuth for enterprise SSO. Before we ship, we need security review from the team.
Options Considered
- Auth0 - managed service, higher cost
- Custom OAuth - more control, more responsibility
- NextAuth.js - good middle ground
We're going with NextAuth.js + custom session handling.
Recommendation
Proceed with NextAuth.js but with custom token storage in Redis for better session management.
Trade-offs
- More complex than pure NextAuth
- But: Better control over session invalidation and multi-device handling
Questions for Team
- Token refresh strategy?
- Session timeout duration?
- How do we handle compromised sessions?
Please ack after reviewing the security implications.
Resolution Summary
ciao sono una risoluzione
Activity
Bob Smith added label Needs Review
Feb 2, 2026, 11:05 AM
Bob Smith added label Urgent
Feb 2, 2026, 11:06 AM
I've reviewed the proposed OAuth flow. A few concerns: 1. Token storage - are we using httpOnly cookies? 2. PKCE implementation - is the code_verifier stored securely? 3. Redirect URI validation - whitelist approach?
test reply
ciaiiii
Another comment chicossss
Prueba
Feb 4, 2026, 07:55 PM
Test User changed status from open to resolved
Feb 4, 2026, 08:04 PM