Forum Discussion
mouadcherkaoui
Feb 04, 2021Brass Contributor
Teams / Federation Authentication / MacOS X Customer
Hi, this question is initially posted in the answers forum: Teams / Authentification Fédéré / Client MacOS - Microsoft Community "We have been having federated connection issues with Teams on...
schloemi67
Mar 07, 2021Copper Contributor
I discovered exact the same problem - always "white screen" and Error 1:403 when closing MS-TEAMS !
In the Log-File always "AD_ERROR_SERVER_USER_INPUT_NEEDED" occurs as the "aquireTokenSilentwithRessource" gets called instead of "aquireTokenwithRessource" !!
I tried everything -> delete/reinstall TEAMS, deleting keychaines, caches, library/Application Support" as mentioned in near every article when running into issues with MS-TEAMS on MacOS.
finally I found the problem: we use "NoMAD" for managing our AD Kerberos Tickets on our company Mac's - when logged into "NoMAD" with my AD-User I don't get the "Prompt" for re-authenticating within MS-Teams - if I don't login into "NoMAD" everything works as it should - first starting MS-Teams and ONLY AFTERWARDS logging into "NoMAD" !!!
this issue caused me all my nerves, as I could only use the browser based Version of MS-Teams and not the DesktopVersion.
This leads to the question if this is a bug only with NoMAD and MS-Teams, or with every AD-Helper installed to MacOS ???
In the Log-File always "AD_ERROR_SERVER_USER_INPUT_NEEDED" occurs as the "aquireTokenSilentwithRessource" gets called instead of "aquireTokenwithRessource" !!
I tried everything -> delete/reinstall TEAMS, deleting keychaines, caches, library/Application Support" as mentioned in near every article when running into issues with MS-TEAMS on MacOS.
finally I found the problem: we use "NoMAD" for managing our AD Kerberos Tickets on our company Mac's - when logged into "NoMAD" with my AD-User I don't get the "Prompt" for re-authenticating within MS-Teams - if I don't login into "NoMAD" everything works as it should - first starting MS-Teams and ONLY AFTERWARDS logging into "NoMAD" !!!
this issue caused me all my nerves, as I could only use the browser based Version of MS-Teams and not the DesktopVersion.
This leads to the question if this is a bug only with NoMAD and MS-Teams, or with every AD-Helper installed to MacOS ???