Hi Sarah -
Please check out this video for the current supported configurations around authentication and authorization:
Out of the box authentication is defaulted to windows integrated security - either local to the machine that QS is installed on, or via the Windows Domain. Other authentication is possible, but provides additional configuration or possibly custom modules .. at the moment. Our team is researching and improving this for the future. Please see this documentation as well to learn more:
Be sure to check the other links and sub-topics too.
Please mark the appropriate replies as helpful / correct so our team and other members know that your question(s) has been answered to your satisfaction.
There are two solutions to this, depending on your environment and your deployment plans.
The easiest way is to restrict access to Qlik Sense for the group by authorization, instead of authentication. This is solved using the rules engine in the QMC. This way of solving it does however require a working AD in your network.
The not-as-easy way is to create your own authentication module and hook it up to a suitable way of verifying your groups credentials. For this you would need to read the proxy API: http://help.qlik.com/sense/en-us/developer/#../Subsystems/Qlik_Sense_Proxy_Service_API/Content/QPS%20API/Proxy_Introduct…
Within it, focus on the authentication api: http://help.qlik.com/sense/en-us/developer/#../Subsystems/Qlik_Sense_Proxy_Service_API/Content/QPS%20API/Proxy_REST_API_…
Once you are up to speed with the APIs, create an authentication program and link it to a virtual proxy in the QMC.