![]() ![]() This solution provides single sign-on capabilities right out of the box. ![]() The identity of the logged-in user is communicated to QlikView Server using either the Kerberos or the NTLM security solution.Later when the user wants to establish a session with a QlikView Server (QVS) (for example, via a browser on the desktop), QVS can use the built-in Integrated Windows Authentication (IWA).The user credentials are validated when the user logs in to the Windows operating system on the client machine.Authentication when Using QlikView Server in a Windows User EnvironmentĪuthentication to a QlikView Server in an environment based on Windows users (for example, incorporating Active Directory) is straightforward. In such a scenario, QlikView relies on the authentication to be performed prior to accessing QlikView, and that some token of identity is transmitted to, and trusted by, QlikView. In the QlikView context, the authentication of a user is almost always done against an external entity that is then used to pass the externally authenticated user identity to QlikView Server. Although the majority of implementations require users to be authenticated, QlikView can also be configured to allow anonymous access ![]() QlikView requires that the user is authenticated when establishing a session via QlikView Server (either through a browser or when downloading and opening a document via the QlikView Desktop client).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |