Qlik Sense: URL with specific characters return Error 400 with ticket authentication in April 2020 Patch 1 and June 2020
Article Number: 000108518 | Last Modified: 2020/08/14
URL with specific characters return Error 400 with ticket authentication in Qlik Sense June 2020.
This also happens with Windows authentication, which is considered one type of ticket authentication in Qlik Sense.Environments:
- Qlik Sense Enterprise for Windows April 2020 Patch 1 and Patch 2
- Qlik Sense Enterprise for Windows June 2020 Initial Release and Patch 1
This defect (QB-1995) is still under investigation by Qlik R&D and new information will be updated when available.
Currently, the below two scenarios are identified as problematic, but it is expected that it impacts a wider range of scenarios using URL parameters.
1. Using filters with the QRS API, for example:
This includes the REST connector or calling the API directly.
2. Using the Single Integration API with some spaces in the selection values, for example: <iframe src='https://qlikserver1.domain.local/single/?appid=b61ef493-2687-405a-a866-cca9108729d6&obj=71de3559-c190-40a3-8790-7d08fd321deb&opt=nointeraction&select=clearall&select=ACCT_CITY,Altamonte%20Springs&qlikticket=y.j_U14d4-OHyvVN' style='border:none;width:100%;height:100%;'></iframe>
In this case, the %20 is provoking the error 400.
From a preliminary investigation, the issue happens during the ticket validation process. If the user first logs in to a URL that doesn't have those URL parameters and obtain a valid session on the Qlik Proxy service, then they will be able to access URL with URL parameters or perform API calls with URL parameters without any issue.