-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Microsoft authentication does not work with NFC #24
Comments
Other apps work fine |
You really need to edit OP to add more details, my man. What browser are you using? How are you trying to auth. Are you tapping the phone while logging in on PC? Or logging in on mobile using NFC, or pc using an NFC reader or anything. Be as specific as possible. |
Sorry I was not specific enough. I am tapping the watch with the phone to login on my mobile phone via NFC. The phone is picking it up as gym equipment rather than passing the security key info to the browser which is Edge, though I have tried other browsers as well. |
Go to settings > Connections > NFC > Others > Disable Samsung health and make sure wearauthn is enabled |
All I see under NFC is "Contactless payments". Under that, neither is listed.
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Ayandaftary ***@***.***>
Sent: Monday, October 9, 2023 9:39:51 PM
To: fmeum/WearAuthn ***@***.***>
Cc: ctgreensboro1 ***@***.***>; Author ***@***.***>
Subject: Re: [fmeum/WearAuthn] Microsoft authentication does not work with NFC (Issue #24)
Sorry I was not specific enough. I am tapping the watch with the phone to login on my mobile phone via NFC. The phone is picking it up as gym equipment rather than passing the security key info to the browser which is Edge, though I have tried other browsers as well.
Go to settings > Connections > NFC > Others > Disable Samsung health and make sure wearauthn is enabled
—
Reply to this email directly, view it on GitHub<#24 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCJ6BYRIATR4GTB7UJB4H6DX6SROPAVCNFSM6AAAAAA4T5FFH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJUGE3TCMZRGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Are you on wear os 4 / Oneuiwatch 5? |
Ah! Settings on the watch. I was looking in settings on the phone. Found it! Thanks!!
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Ayandaftary ***@***.***>
Sent: Tuesday, October 10, 2023 9:35:52 AM
To: fmeum/WearAuthn ***@***.***>
Cc: ctgreensboro1 ***@***.***>; Author ***@***.***>
Subject: Re: [fmeum/WearAuthn] Microsoft authentication does not work with NFC (Issue #24)
All I see under NFC is "Contactless payments". Under that, neither is listed.
Are you on wear os 4 / Oneuiwatch 5?
Heres the others section on my watch6 Screenshot<https://i.imgur.com/Ad0u4tp.png>
—
Reply to this email directly, view it on GitHub<#24 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCJ6BYQZVKKLLXYWPOJUKBTX6VFLRAVCNFSM6AAAAAA4T5FFH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJVGQ2DGNZUG4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
What went wrong?
Using a browser to login to Microsoft account, NFC does not work
Steps to reproduce
Which model is your watch?
If you don't know your watch's model, you can find it under Settings -> System -> About.
Galaxy Watch 5
Which Android version is running on your watch?
You can find it under Settings -> System -> About -> Version.
Which version of WearAuthn are you using?
You can find the version of WearAuthn you are currently using in the About screen available from the app's main menu.
Screenshots
If you think that it could be useful, consider adding a screenshot. To take a screenshot of your watch, open the "Wear OS by Google" app on your phone, open the ⋮ menu in the top right and select "Take screenshot of watch". After a few seconds, you will receive a notification on your phone that allows you to download or share the screenshot.
The text was updated successfully, but these errors were encountered: