Repository navigation
Unable to authenticate with Edge + Intune security controlled devices #533
Description
Describe the bug
When authenticating with sameDevice using Edge, using Microsoft Intune controlled phones(iOS).
- It asks "This site is trying to open another application." Click Allow
- Popup: "Something went wrong. The application couldn't be opened".
- Then it stays spinning on the login screen, where "Avbryt" is your only option -> this leads to the "No such order" error sort of described in Multiple collect attempts after collect already completed, causing the flow to fail #508 , because the flow has not been properly initiated, there is no order. Switching manually to BankID app does not help. It has not been triggered.
We do not control the Intune settings so I cannot say which is causing it, but some security restriction must be.
However - attempting locally to making the library open according to BankIDs documentation (https links instead of bankid:// links - it works without issues).
What area is it related to
UI
To Reproduce
Steps to reproduce the behavior:
- Go to demo.activelogin.net with an affected device
- Click on Login
- Click on Use BankID on this device
- It asks "This site is trying to open another application." Click Allow
- Error : "Something went wrong. The application couldn't be opened".
Expected behavior
BankID being opened.
NuGet package version
What version of the Nuget package are you using? Latest and demo-site is uncoupled from what we use.
Runtime version
Are you using .NET Core / .NET Framework? What version?
.NET 8, and whatever Demo siteuses:
Smartphone (please complete the following information):
- Device: iPhones (several different tested)
- OS: iOS 26 but also older
- Browser : Edge
- Version: 143.0.3650.112
Activity
elinohlsson commentedon Jan 9, 2026
Thanks for the detailed report.
I haven’t been able to reproduce this issue myself, as I don’t have access to a Microsoft Intune–controlled iPhone.
However, updating Active Login to conform with the current BankID recommendations for autostart (using the documented HTTPS-based links instead of the
bankid://scheme) sounds like a good starting point and is something we need to address regardless.I’ve created a separate issue for this: #534, and will prioritize implementing it. I’ll also review your open pull request #526, which appears to be related.
If the problem persists after these changes, we can investigate additional actions.
For reference, the demo site
demo.activelogin.netis currently running Active Login v11.1.2.elinohlsson commentedon Sep 24, 2026
We have made changes related to launching the BankID security application in the latest release, v12.1.0. See the release notes for details.
Active Login now uses the BankID-recommended https://app.bankid.com approach for launching BankID on mobile devices instead of relying on the
bankid://scheme.This work was inspired in part by your investigation and the implementation in #526. However, we had to make some changes to the proposed implementation, so the implementation in v12.1.0 is not identical to the one proposed in that PR.
On iOS, Active Login now uses the new App Link approach for all browsers. On Android, we had to keep the existing approach for Samsung Internet, Firefox, and Edge, as we could not get the complete launch and redirect flow working reliably with https://app.bankid.com in these browsers.
Since we don't have access to a Microsoft Intune-controlled iPhone, we have not been able to verify this particular scenario ourselves. I'll therefore keep this issue open for now.
@urizen-source If you are able to test this with v12.1.0 on an affected Intune-controlled iPhone, it would be great to know whether the issue is resolved.
If the issue is still present, please let us know and include any relevant details about the iOS, Edge, and Intune configuration if available.