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

[Feature Request]: Using Clerk Management Authentication #524

Closed
4 tasks done
lolpanda2004 opened this issue Jul 28, 2024 · 7 comments
Closed
4 tasks done

[Feature Request]: Using Clerk Management Authentication #524

lolpanda2004 opened this issue Jul 28, 2024 · 7 comments
Labels
enhancement New feature or request

Comments

@lolpanda2004
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Feature Description

By using clerk authentication, its easier to create customized log in page and sign up page (including form validation) and other options to login in through google, github etc. Thus it will enhance like validation and easy for users to log in via other options rather than manually typing it out.

Use Case

By using clerk authentication, its easier to create customized log in page and sign up page (including form validation) and other options to login in through google, github etc. I would consider this as an alternative to the already existing page.

Benefits

It would be much more easier to save the data in the free trial version of it and secure the users data. Easier for the users to log in via multiple options as well.

Add ScreenShots

No response

Priority

Low

Record

  • I have read the Contributing Guidelines
  • I'm a GSSOC'24 contributor
  • I have starred the repository
@lolpanda2004 lolpanda2004 added the enhancement New feature or request label Jul 28, 2024
Copy link

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊

You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

@VaibhavArora314
Copy link
Owner

Are there any secrets on the client side? As with the current deployment approach we cannot pass any secrets or env variables to the client side.

@lolpanda2004
Copy link
Contributor Author

Yus there is but we can create an env example file that can go through the deployment the client would have to use their credentials (we can specify in comments or in documentation where to find the necessary credentials). So in their local computer, they can change the values in env.example file but then they need to create an env file and replace this with the content. At the end, they should remove the env file. Do note that documentation for this might be updated as well.

@VaibhavArora314
Copy link
Owner

If we add env variables in .env for deployment then we will have to commit it to GitHub which is not a solution I think.

@VaibhavArora314
Copy link
Owner

Is there any other way since we are serving build of react app via express server

@lolpanda2004
Copy link
Contributor Author

As far as I know this is the only way to work with clerk through the .env file

@VaibhavArora314 VaibhavArora314 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 10, 2024
Copy link

Hello @lolpanda2004! Your issue #524 has been closed. Thank you for your contribution!

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

No branches or pull requests

2 participants