https://supertokens.com/
Join Discord
Is there any guidance on how we might implement biometric auth for a thirdparty. In this case we're ...
# support-questions-legacy
g
Is there any guidance on how we might implement biometric auth for a thirdparty. In this case we're wanting to use google. We have the social signup working but are currently researching how we might add a biometric login with it.
r
Hey @garrett7056
I assume that you want to add this as a second factor?
Or do you mean a flow where the android app implicitly takes the Google’s credentials after a successful biometric auth? Similar to how iPhones do for apple login?
g
The latter.
r
This would be something that needs to be done via a native SDK for android. Perhaps @nkshah2 can shed some light
g
Thank you!
Some more detail that might be helpful: Our current plan is to build a native app that is basically just a native login screen and the rest of the app is a webview.
n
Hi, Google actually provides a sample app that explains how you would go about adding biometric login to your app and how you can hook it up with regular auth https://developer.android.com/codelabs/biometric-login#0
Their sample uses email password auth but the same steps should apple to social auth as well
r
apply*
n
Before you explore the example app, are you looking to just prompt the user for biometric and then take them through a separate flow for social login?
g
I guess it's just not clear to me where the integration point is with supertokens.
do we pass something to thirdPartySignInAndUp()?
n
Right so for the native android SDK you would call the APIs exposed by SuperTokens manually and the android sdk would handle sessions and auto refreshing for you
From an integration point of view you would first complete sign in with google using the official package
And then use the id token that google returns and call the signInUp endpoint that SuperTokens provides
g
Gotcha - so to recap: 1. use Google's official package in the native app 2. Send the user through that flow 3. On success, take the id token google returns and pass it to the webview 4. now in the supertokens JS SDK, call thirdPartySignInAndUp() passing it the id token?
r
You don't need to pass it to the web view. You can just call the backened API from the android app directly with the id token and use our android SDK for session management
g
and our app's webview using the JS SDK will all work as well?
r
ohh so if you are using the web view in your app already, then yea, you need to pass the id token to that
n
You could pass it to the webview if you don’t have any logic on the native side that needs auth protection
If you need auth protection on both native and web then I think there’s a way to have both use the same cookie store on android
r
g
awesome - and that andriod link you sent me details how to store the id token from google - I think that covers all my questions.
Thanks to both of you!
r
sounds good. Let us know if you get stuck anywhere 🙂
PreviousNext
Powered by

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by