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

Example of SIWE custom integration with NextAuth #187

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

marc-aurele-besner
Copy link
Member

Example of SIWE custom integration with NextAuth

image
image
image
image

This is just a crude example of a sign-in with ethereum (SIWE) flow, it's crude, the final handshake with the auth endpoint is not implemented and it's missing some better edge case detection on the client side.

Copy link

netlify bot commented Feb 7, 2025

Deploy Preview for auto-drive-demo failed. Why did it fail? →

Name Link
🔨 Latest commit e0b7d8f
🔍 Latest deploy log https://app.netlify.com/sites/auto-drive-demo/deploys/67d202195ba9eb0008c2f269

Copy link

Report too large to display inline

View full report↗︎

Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Obfuscated code npm/@polkadot/util-crypto@13.4.3 ⚠︎

View full report↗︎

Next steps

What is obfuscated code?

Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware.

Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/@polkadot/util-crypto@13.4.3

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.

2 participants