That is simply going from the domain login to the email address like this:Īnother option that worked was to use the Down-Level logon name (Domainusername) It seems that with the upgrade of ADFS it now required the UPN (user principal name / MSDN – User Name Formats) login in order to authenticate. To resolve the issue it was a very simple change. My account was fine and I could still access Dynamics CRM through the browser just fine but Scribe would not connect for anyone. ![]() This was working fine but suddenly it failed with the ID3242 error message. Previously, our connection to Dynamics CRM was defined with a domain level login like below: Turned out the certificates were about to expire and some work was happening related to that as well as an ADFS upgrade taking place. Our connections were working fine a few days earlier and so we looked at what had changed. In our case, none of these things seemed to be the problem. ![]() I recently had this issue at a client and we spent some time trying to resolve it based on many other posts, most of which referred to Active Directory Federation Services (ADFS) configuration, audience permission settings and other suggestions. ![]() Are you trying to connect to Microsoft Dynamics CRM from Scribe Insight and getting the error message “ID3242: The security token could not be authenticated or authorized”?
0 Comments
Leave a Reply. |