Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
The issue only affects Microsoft's endpoints, such as sharepoint, onedrive and dynamics CRM services.When using "Consent" or "None" in the "Prompt / consent level " parameter the following error message is thrown:
AADSTS90027: We are unable to issue tokens from this API version on the MSA tenant.Please contact the application vendor as they need to use version 2.0 of the protocol to support this.
Using the CanAuthentcate table select "select_account" in the "Prompt / consent level" parameter.
Product Defect ID: QB-4951
Thanks for the information. Unfortunately, the workaround does not work for us. If I enter the Base URL, Set "Prompt / consens level" to select_Account and click on Authentication Code I get an Authentication Code which I can paste into the "Authentication Code" field. Then I click on Save and try to establish a connection by clicking on "Save Inputs & Run Table". But then I will get the message "Authenticated = false"; "Error Message = No refresh_token found".
Are we doing it wrong?
Hello @danielbuhl ,
It's likely that the problem that you are facing is not related to this article.
I would suggest checking if you are using the latest version (june 2021) and if the proxy is correctly configured on the deploy.config file in case that you are using a proxy.
many thanks for the hint with the proxy configuration. I did not change the proxy entries but this topic leads me to our firewall admin. He did some analysis and found out that the request did not reach the CRM System via the new connector. He did some changes in the firewall configuration and now we are able to get a connect with the Dynamics connector V2. Thank you.
I assume the latest release of Qlik Web Connectors - June 2021 Patch 1 - resolves this looking at the release notes.
Excerpt from the release notes:
Qlik Microsoft Dynamics CRM Connector V2Updated to use v2.0 of authentication API (fixes error AADSTS90027 during consent/authentication).