irp
New Contributor
Joined 2 years ago
User Profile
User Widgets
Contributions
Azure MFA with phishing resistant authentication
We are struggling to get Azure MFA set up. We purchased the license that permits that. That is the only reason we bought that license. We use phishing resistant MFA such as FIDO key and Windows Hello. Microsoft has been releasing conditional access rules for "require phishing resistant MFA for admins" and those rules will be set up for all at the end of Dec. All our admins only have FIDO keys - no passwords, We have set SSO up with Adobe, AutoDesk, Trimble, AFI.AI and another ERP I will not name. But, GoTo does not work. The messages we get are Sorry, but we’re having trouble signing you in. AADSTS75011: Authentication method 'X509, MultiFactor' by which the user authenticated with the service doesn't match requested authentication method 'Password, ProtectedTransport'. Contact the GoToMyPC application owner. Or AADSTS75011: Authentication method 'MultiFactor, Fido' by which the user authenticated with the service doesn't match requested authentication method 'Password, ProtectedTransport'. Contact the GoToMyPC application owner This implies that 1. GoTo is not really supporting all of Azure's authentication. and 2. GoTo probably is not using phishing-resistant MFA internally in their own org. Adversary in the middle attacks are what 99% of phishing attacks are these days, so we need to protect ourselves, especially the admin accounts, using phishing resistant MFA. I have tried explaining this to support and I get "we support Azure MFA" as an answer. It probably should be "we support phishing-susceptible MFA but not phishing-resistant Azure MFA."1.3KViews0likes5CommentsNone of the "my account: links work
I am trying to log in to change billing, etc. When I log into "GoToMyPC" there are links on the left Billing Plan Selection Account History Settings None of these work. I said, "self, maybe work is blocking something" so I tried my home computer. Nope. I said, "self, take your phone off wireless and try that." Nope. I think said, "hmm, let me get a Server 2016 VM from Azure that definitely has limited security, filtering, etc. and try that." None of these work. I have tried Chrome, Edge, Firefox and Brave. The site won't load on IE on Server 2016, which is not unexpected. On error is for cdn.pendo.io/agent/static//pendo.js. Note the two slashes before pendo. Failed to load resource: the server responded with a status of 403 () GET https://cdn.pendo.io/agent/static//pendo.js net::ERR_ABORTED 403 (Forbidden) So far we have been unsuccessful explaining to tech support that the link is not working. We don't need a guide, we need the link to work. Developer tools from the browsers show issues with CORS (cross origin resource sharing" and info about cookies being set up wrong. This seems like a dev problem - users to write cookies.Solved945Views0likes3Comments