Back to Blog
Macos azure ad login6/3/2023 Issue by changing the response mode your provider uses from a POST toĪ GET request, using the following code. If you are using external OIDC providers you may be able to avoid the If you are using ASP.NET Core Identity you disable the protection byĬonfiguring cookies with the following code services.ConfigureExternalCookie(options => ) There is a solution documented by the aspnet/security team on GitHub. Is there any update, reasoning, or resolution to resolve/workaround the problem behind the Safari and Microsoft login redirection issue? NoMAD Login provides this, and more, by allowing for AD logins on macOS without the need to bind to Active Directory. This redirection from server and browser seems to be the main reason behind the infinite redirection. The cookie is still not sent along with the request, causing the server to send the user back to the login page. However, the browser still has some identity information which causes the user to automatically log in again, redirecting to the server. ![]() This is most likely due to Safari not letting the Microsoft cookie through, which causes Microsoft's servers to redirect back to the login page to get the cookie required. ![]() This new update causes Safari on Apple device users to go into a redirect infinite loop when logging in. ![]() The updates on Safari 12 are shown here: ĭue to some of the new Security and Privacy updates, there seems to be a cookie issue that is causing infinite redirection when logging into the endpoint: ![]() There seems to be a current issue with logging into Microsoft Online with Mac OS and iOS devices utilizing the newest version of Safari (12).
0 Comments
Read More
Leave a Reply. |