WPIntell

Source evidence

Microsoft emails issue

Passwordless Login · support · 2021-04-06T18:40:00+00:00

Passwordless Login plugin evidence original source source API
mixedsentiment
mediumseverity
0.78relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 33 rows with source links

15.2% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
nguruswamy resolved
Hi, I am testing setup of passwordless login for our website. It works fine with Yahoo and Gmail accounts but when I use Microsoft 365 emails I get the message “Your token has probably expired. Please try again” even if it has only been a couple of minutes since the email was sent. I have tried with aliases as well – no luck. Any advice to troubleshoot this issue? Cheers, N. The page I need help with: [ log in to see the link] Hi @nguruswamy , This is happening due to the antivirus provided by Microsoft 365. Basically, when that email is received, it automatically clicks on the link in order to verify it. So when the user clicks on that link, it counts as the second time, so it shows as expired. Kind regards, Thanks for the explanation, Madalina. Are there any workarounds? Hi @nguruswamy , Unfortunately at the moment, we do not have a workaround for this issue.

Comments

3 shown
Madalina Ruzsa 2021-04-07T13:41:00+00:00

Hi @nguruswamy , This is happening due to the antivirus provided by Microsoft 365. Basically, when that email is received, it automatically clicks on the link in order to verify it. So when the user clicks on that link, it counts as the second time, so it shows as expired. Kind regards,

nguruswamy 2021-04-08T05:25:00+00:00

Thanks for the explanation, Madalina. Are there any workarounds?

Madalina Ruzsa 2021-05-13T11:20:00+00:00

Hi @nguruswamy , Unfortunately at the moment, we do not have a workaround for this issue.