Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
samith_sgh
Partner - Contributor II
Partner - Contributor II

How to stop brute force attacks on Qlikview Access Point?

We use Windows Active Directory for Qlikview Access point authentication. Even though we have added a AD password lockout policy, user logins does not get locked out when a brute force attack on Access Point. Is there a special way to add AD password lockout policy to work with Qlikview? Or is there other ways to stop brute force attacks?

Labels (1)
1 Solution

Accepted Solutions
marcus_sommer

I don't know how the authentication is implemented and if there is a forward and backward communication between QlikView and the AD available and which settings it might need (in QlikView as well as within the network in regards to open ports and similar stuff).

Another theoretically option which I could imagine may exists (again I don't know) might be to activate within QlikView a measurement which stops the login after n times and/or increasing the time between possible logins or similar stuff. It would be not perfect in regard to your question but would preventing a massive brute force attack.

A further possibility may be to implement a SSO solution which would completely remove the necessity of a QlikView login.

View solution in original post

1 Reply
marcus_sommer

I don't know how the authentication is implemented and if there is a forward and backward communication between QlikView and the AD available and which settings it might need (in QlikView as well as within the network in regards to open ports and similar stuff).

Another theoretically option which I could imagine may exists (again I don't know) might be to activate within QlikView a measurement which stops the login after n times and/or increasing the time between possible logins or similar stuff. It would be not perfect in regard to your question but would preventing a massive brute force attack.

A further possibility may be to implement a SSO solution which would completely remove the necessity of a QlikView login.