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

[Help Needed] Implement Dual Authentication Support for Supabase Auth and Clerk in Next.js #87

Closed
daniel-farina opened this issue Nov 21, 2023 · 1 comment

Comments

@daniel-farina
Copy link
Collaborator

daniel-farina commented Nov 21, 2023

Goal

The objective is to extend our authentication capabilities to include Clerk as an alternative to Suppabase. This integration should allow for seamless switching between the two services through environment variable configurations.

Requirements

  • Complete [Help Needed] Transition from NextAuth to Supabase Auth for User Authentication #91 first
  • Integrate Clerk alongside Suppabase in the authentication flow.
  • Ensure that the authentication helpers are adaptable for use with both Supabase Auth and Clerk.
  • The switch between Supabase Auth and Clerk should be manageable by setting the appropriate .env variables.
  • Document the changes comprehensively in a single feature branch PR.

Expected Outcome

A successful contribution will result in a flexible authentication setup where either Supabase Auth or Clerk can be used interchangeably based on simple environment variable toggles, without affecting the existing authentication functionality.

Contribution Process

  1. Express your interest by commenting on this issue to prevent overlapping work.
  2. Fork the repository, and create a feature branch for this task.
  3. Implement the integration while ensuring that both authentication systems can coexist and are selectable via .env variables.
  4. Thoroughly test the implementation to ensure that both systems work independently when chosen.
  5. Open a Pull Request with a detailed list of changes and testing procedures for review.

Additional Notes

  • The implementation should not break the current default authentication method.
  • Keep changes minimal and modular to facilitate easy review and potential rollback.
  • Ensure backward compatibility for existing users who might not switch to Clerk immediately.

This feature is critical for users who prefer Clerk or require its specific functionalities, and your contributions towards this dual authentication capability will significantly enhance the flexibility of our application.

Thank you for considering this contribution; we are excited to see your innovative solutions!

@daniel-farina daniel-farina changed the title [EPIC] Add Clerk support [Bounty] Implement Dual Authentication Support for NextAuth and Clerk in Next.js Nov 21, 2023
@daniel-farina daniel-farina changed the title [Bounty] Implement Dual Authentication Support for NextAuth and Clerk in Next.js [Help Needed] Implement Dual Authentication Support for NextAuth and Clerk in Next.js Nov 21, 2023
@daniel-farina daniel-farina changed the title [Help Needed] Implement Dual Authentication Support for NextAuth and Clerk in Next.js [Help Needed] Implement Dual Authentication Support for Supabase Auth and Clerk in Next.js Nov 21, 2023
This was referenced Nov 22, 2023
@daniel-farina
Copy link
Collaborator Author

Not pursuing for now

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

No branches or pull requests

1 participant