Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(express): add role-based authentication documentation for express #12618

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Exe16Kishan
Copy link
Contributor

Added comprehensive guide for Express.js role-based authentication, addressing missing documentation for this common use case. Key additions:

  • Type declarations and interfaces for role management
  • JWT strategy with role handling (tested with Google OAuth)
  • Prisma adapter integration showing database persistence
  • Code examples following Auth.js best practices
  • Schema setup for storing user roles

Guide follows Auth.js documentation standards and builds on existing OAuth/database adapter guides. All code examples tested locally.

Fills documentation gap for Express.js implementations. Ready for review.

Add detailed guide for implementing role-based authentication in Express using Auth.js.

Changes include:

Step-by-step instructions for setting up RBAC with Auth.js
Best practices for managing roles and permissions
Updated documentation to align with Auth.js v5 conventions
@Exe16Kishan Exe16Kishan requested a review from ndom91 as a code owner February 6, 2025 16:17
Copy link

vercel bot commented Feb 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
auth-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 6, 2025 4:21pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
next-auth-docs ⬜️ Ignored (Inspect) Visit Preview Feb 6, 2025 4:21pm

Copy link

vercel bot commented Feb 6, 2025

@Exe16Kishan is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

@Exe16Kishan
Copy link
Contributor Author

Hey team! It looks like the merge is blocked because it needs an approval and the Vercel deployment is waiting for authorization. Could someone with write access take a quick look and review the PR? Would really appreciate it—thanks a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant