microsoft-authentication-library-for-objc: Microsoft login page freezes for existing users after upgrading from ADAL to MSAL
Recently we upgraded our app from ADAL to MSAL. While the new app launches and works fine for new users, the Microsoft login page freezes for existing users (who were already enrolled into MAM policy using ADAL app). My understanding was that since the Keychain sharing cache is common (adalcache), this transition would be smoother. Is that understanding wrong for some reason?
One thing to note is with ADAL, we did not have the ADALClientId key added to the info plist and I think it was enrolling by creating a default ClientID. After upgrading to MSAL, we had to add the ADALClientId and ADALRedirectUri under the IntuneMAMSettings dictionary key of Info Plist file. Can this be the reason for the up login screen to freeze up?
How to fix the issue for users who were already enrolled?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 43 (8 by maintainers)
Great to hear the hang is now resolved!
hi @Kyle-Reis, I believe everything is now working as expected. I no longer hang and am able to get through and get an app policy.
We do have brokered auth configured, and the first run after bumping to the new versions prompted me to enter in my microsoft credentials even though I’m signed in to the Authenticator app already. After signing in, I was unable to see this happen again and brokered auth seems to work correctly after subsequent uninstalls/reinstalls/etc.
Would that first time login prompt expected somehow, maybe related to the account enrollment situation I was in? I just want to make sure there aren’t any related regressions.
Hi @bblia, try setting MSALGlobalConfig.loggerConfig.logLevel to MSALLogLevelNothing before calling loginAndEnrollAccount.
@Kyle-Reis could you help @bblia to take a look at the trace? 😃