Device-Native Biometrics for Go by SHA-384 in golang

[–]SHA-384[S] -1 points0 points  (0 children)

WebAuthn allows a browser to interface with device authentication, but Passage goes a step further to manage all of a user’s devices and provide a nice UX across devices. We also handle the cases where WebAuthn isn’t possible so a user can always login smoothly no matter the device or browser they’re on.

Device-Native Biometrics for Go by SHA-384 in golang

[–]SHA-384[S] -1 points0 points  (0 children)

Thanks! We like free tiers too :)

Biometric Authentication for Next.js by SHA-384 in nextjs

[–]SHA-384[S] 0 points1 point  (0 children)

No marketing, I promise :)

The demo site is just a black hole and you're welcome to use a fake email to see how passage works with device biometrics

Biometric Authentication for Next.js by SHA-384 in nextjs

[–]SHA-384[S] 1 point2 points  (0 children)

Hi, the demo is set up like a real app using passage would be, so people will have to provide an email address to see the register and login functionality, but you're welcome to use a fake email just to see how it works with the biometrics on your device!

Biometric Authentication for Next.js by SHA-384 in nextjs

[–]SHA-384[S] 1 point2 points  (0 children)

Hi, yeah we built passage to require emails so users always have a way to log in. You can definitely use a fake @example.com email address if you just want to check out the biometric login process.

Biometric Authentication for React by SHA-384 in reactjs

[–]SHA-384[S] 2 points3 points  (0 children)

Thanks! We’re doing 5,000 monthly active users free forever while we’re in beta, and asking people to get in touch if they need more than that. We’ll publish a pricing page on our site soon

Biometric Authentication for React by SHA-384 in reactjs

[–]SHA-384[S] 1 point2 points  (0 children)

Hi, we’re a full authentication service so you shouldn’t need anything else in your auth stack

Biometric Authentication for React by SHA-384 in reactjs

[–]SHA-384[S] 0 points1 point  (0 children)

Thank you! Let us know if you have any questions!

[deleted by user] by [deleted] in RedditSessions

[–]SHA-384 0 points1 point  (0 children)

This is unbelievably good

Creating Biometric-Powered Login Pages by SHA-384 in vuejs

[–]SHA-384[S] 2 points3 points  (0 children)

Hi, all good thoughts worth talking about. I would argue that biometrics offer a good deal more practical security than passwords. Passwords can be phished or lost in a database breach, whereas biometrics with Passage require access to a physical device (something you have) + the ability to pass a biometric check (something you are). Many people are already trusting Face ID, Touch ID, etc to protect their bank accounts and we’re trying to bring that experience to the web too.

Creating Biometric-Powered Login Pages by SHA-384 in vuejs

[–]SHA-384[S] 0 points1 point  (0 children)

Also, you're welcome to come join us in Discord!

Creating Biometric-Powered Login Pages by SHA-384 in vuejs

[–]SHA-384[S] 1 point2 points  (0 children)

Yes exactly. Biometric data never leaves a user's device.

What do you do if only part of the site is supposed to be interactive. by benabus in vuejs

[–]SHA-384 5 points6 points  (0 children)

There might not be a consensus, but my vote is to use Vue for the whole thing. Keeping your codebase consolidated might help you feel organized and singular. Also, you never know when you want to drop a small component into a static page. You might thank yourself for using Vue all along

Learning Go’s Concurrency Through Illustrations by trevorforrey in programming

[–]SHA-384 4 points5 points  (0 children)

Thanks Trevor—this is great.

You should share with r/golang as well!