Authentication Issue in Qlik Sense Mobile App Using Ticket-Based Client Authentication URI

[anjali24]

I am developing a custom authentication solution for Qlik Sense Enterprise that bypasses the default login screen. While the flow operates smoothly on desktop browsers, it encounters issues in the Qlik Sense native mobile app.
We have implemented a custom SSO solution for Qlik Sense Enterprise that functions correctly on desktop browsers, but fails in the native mobile app. Both the qlikticket and sessionId methods show different failures.

Current Implementation:
Custom Login Page: Users authenticate through a custom portal.
Ticket Generation: Upon successful validation and user authentication, I generate a qlikticket using the QPS Ticket API (/qps/ticket).

note: I also have tried creating the sessionId using qlikticket and passed in query parameter getting same issue. 

Redirect to Qlik:

Desktop (Works) https://qliksenseserver.qlik.com/sense/app/<appId>?qlikticket=<ticket>

Mobile (Fails): Attempts made:

1. qliksenselink://qliksenseserver.qlik.com/sense/app/<appId>?qlikticket=<ticket>
   Error: "Server Login Attempt Failed."
2. qliksenselink://qliksenseserver.qlik.com/sense/app/<appId>?sessionId=<session>
   Error:Displays login screen (not bypassed).
3. qlik://qliksenseserver.qlik.com/sense/app/<appId>?qlikticket=<ticket>
   Error: "Invalid Link."

Expected Behavior: The mobile app should open the specified app without requiring a login prompt, similar to the desktop experience.

Troubleshooting Completed: 

• Verified that the qlikticket works in the browser (https:// URL).
• Confirmed that the virtual proxy is configured for ticket authentication (works for desktop).
• Ensured the latest version of the Qlik Sense mobile app is in use (updated).
• Analysed server logs, which indicate ticket validation failures exclusively for mobile.

Request for Support:

1. What is the correct URL scheme for mobile deep linking with qlikticket?
2. Should it be qlik:// or qliksenselink://?
3. Is the parameter qlikticket or qlik-ticket?
4. Are there additional headers or server-side configurations required specifically for mobile?
5. Are there known limitations regarding ticket authentication in mobile apps?
6. What debugging steps do you recommend to determine why tickets work in browsers but fail on mobile?

[anne789d]

---

@anjali24 wrote:

I am developing a custom authentication solution for Qlik Sense Enterprise that bypasses the default login screen. While the flow operates smoothly on desktop browsers, it encounters issues in the Qlik Sense native mobile app.
We have implemented a custom SSO solution for Qlik Sense Enterprise that functions correctly on desktop browsers, but fails in the native mobile app. Both the qlikticket and sessionId methods show different failures.

Current Implementation:
Custom Login Page: Users authenticate through a custom portal.
Ticket Generation: Upon successful validation and user authentication, I generate a qlikticket using the QPS Ticket API (/qps/ticket).

note: I also have tried creating the sessionId using qlikticket and passed in query parameter getting same issue. 

Redirect to Qlik:

Desktop (Works) https://qliksenseserver.qlik.com/sense/app/ peryourhealth<appId>?qlikticket=<ticket>

Mobile (Fails): Attempts made:

1. qliksenselink://qliksenseserver.qlik.com/sense/app/<appId>?qlikticket=<ticket>
   Error: "Server Login Attempt Failed."
2. qliksenselink://qliksenseserver.qlik.com/sense/app/<appId>?sessionId=<session>
   Error:Displays login screen (not bypassed).
3. qlik://qliksenseserver.qlik.com/sense/app/<appId>?qlikticket=<ticket>
   Error: "Invalid Link."

Expected Behavior: The mobile app should open the specified app without requiring a login prompt, similar to the desktop experience.

Troubleshooting Completed: 

• Verified that the qlikticket works in the browser (https:// URL).
• Confirmed that the virtual proxy is configured for ticket authentication (works for desktop).
• Ensured the latest version of the Qlik Sense mobile app is in use (updated).
• Analysed server logs, which indicate ticket validation failures exclusively for mobile.

Request for Support:

1. What is the correct URL scheme for mobile deep linking with qlikticket?
2. Should it be qlik:// or qliksenselink://?
3. Is the parameter qlikticket or qlik-ticket?
4. Are there additional headers or server-side configurations required specifically for mobile?
5. Are there known limitations regarding ticket authentication in mobile apps?
6. What debugging steps do you recommend to determine why tickets work in browsers but fail on mobile?

---

The "Server Login Attempt Failed" error when deep linking into the Qlik Sense mobile app with `qlikticket` stems from the app's inability to directly process tickets like a desktop browser; it requires an **already established session**. The correct deep link format is `qliksenselink://...sessionId=<session>`. The recommended solution is to first establish a Qlik Sense session through your virtual proxy's **Client Authentication Link (CAL)** in a browser (or WebView), and then trigger the mobile app deep link, now leveraging the active session. Debugging with mobile proxy tools can reveal detailed network request failures.