FusionAuth’s Post

Transcript

So recently we received from someone the battle card that 0 uses against Fusion off in their sales calls and I thought it'd be really fun to go item by item and show where they are wrong. So the first one here is around their password list and I'll admit we don't have SMS password list yet it's on our road map. So that should be coming out in Q3 I believe. But they claim over here that. Use magic links and that they get corrupted in your mailbox. So let's go ahead and explore this. So I I have Docker running with Fusion Auth, which something that at 0 can't do. So I have this running locally. And if we come over here and look, I've gone ahead and set up a local application to use password lists. And so I'll grab this link here. I'll go ahead and start an Incognito window, paste that in. And as you can see, it has the the login with magic link, which is essentially passwordless the way that Fusion auth handles this. Is that it does send me an e-mail and it does use a one time password. So we call these external identifiers and what those do is they essentially link a very long one time password to a user. Not only is Austereo incorrect when they say that it will get corrupted in the mailbox if you're not, is one of the only providers that prevents that. So if I run a jump over to my e-mail here and I grab this link. You know, we can look and you can see that there's a the one time password here on the link. But if I grab this and I post it into a new Incognito window. Start a new one. Here we actually prevent. Mangling of those links because we require confirmation when the browser window is not known. And so we do this to prevent link checkers, Lync scrapers like e-mail readers, any of those tools from traversing through our one time password code that's on the URL. So we drop you to this confirmation page when the browser is not known. And since this is an Incognito window, it's simulates the same case. Where you might open that link in a different browser or you might open it on your phone instead of your desktop. And so in this case, we require user interaction, which is the only and the safest way to prevent Lync mangling or Lync eating. And so once I click that, I don't really have a server connected. I'm, you know, not running anything beyond Fusion auth. But as you can see, we've prevented the issue that Zero has claimed that we have here. So this is just the first one. I'll keep doing these videos. I think they're fun. And yeah, hopefully you can see the value and the the benefit of using Fusion Auth overall zero. Thanks.