Why QlikView asks for verification twice?

[Jazimjj]

Hi there, I recognize this query has already been requested withinside the beyond but, still, I can not discover a solution.

Which will be the motives why QlikView suggests the following (odd) login shape after a primary a success login made thru the same old shape, whilst the person attempts to go into a document?

It would not take place for all customers nor for all applications.

Any ideas?

[Jill_Masinde]

@Jazimjj Do you have section access on the documents? Try and verify if the effected applications have Section access in play.  Below articles provide more information on section access;

https://help.qlik.com/en-US/qlikview/May2022/Subsystems/QMC/Content/QV_QMC/QMC_Users_SectionAccessMa...

https://community.qlik.com/t5/Knowledge/Section-Access-Best-Practice-Guidance/ta-p/1712333

[Jill_Masinde]

@Jazimjj Were you able to resolve this issue?  Kindly mark  "Accept as Solution".

[icemachine29]

If you are seeing this then you need to speak to the administrator/owner of this app and have them update your section access credentials.
If you do not have section access credentials, you need to ask the owner to add you to the section access load script.

[contempo · Accepted solution]

The QlikView software services ask for authentication (either through directory catalogue or by userID and password). Once authenticated, there are two types of users, ADMIN and USER type. The level of authorization or data access decide by what type of users. The admin has access to all the documents.

[SimonZahra]

To troubleshoot and resolve this issue:

• Verify that the QlikView server, document, and user settings are configured correctly.
• Clear browser cache and cookies to rule out any browser-related issues.
• Test the behavior on different browsers or devices to see if it's specific to a certain environment.
• Review any logs or error messages that might be generated during the failed login attempts.
• Check if this issue occurs consistently for certain users or specific documents.

If the issue persists and you're unable to determine the cause, reaching out to QlikView's official support or community forums might provide you with more tailored assistance based on your specific environment and circumstances.

[CorteizHoodie]

1. Authentication Configuration

QlikView supports multiple authentication methods, such as Windows authentication, form-based authentication, or custom solutions. If the system is configured with dual-layered authentication (e.g., Windows Authentication followed by a QlikView AccessPoint login), it may require users to verify their identity twice.

---

2. Browser or Session Settings

When using QlikView through a web browser:

• Session Cookies: If cookies are disabled or cleared frequently, the browser might not retain session data, causing the user to log in again.
• Timeout Settings: If there is a session timeout between the two verifications, the system may ask the user to authenticate again.
• Third-Party Browser Plugins: Some plugins or privacy settings might block certain cookies or scripts, disrupting single-sign-on (SSO) or session continuity.

---

3. Multiple Portals or Services Access

If QlikView integrates with other systems, such as a portal or external dashboard, navigating between them might trigger separate authentication processes:

• Accessing QlikView AccessPoint and a QlikView document (via AJAX or plugin) might need independent verifications.
• If SSO is not properly configured, users may face duplicate login prompts.

---

4. License or Token Verification

If the license management server or access token system requires additional checks to ensure compliance, QlikView might ask for secondary verification. This is more common in cases where:

• User licenses are allocated dynamically.
• Token limits are reached, and QlikView needs confirmation of user allocation.

---

5. Network Configuration