1. Is the session CAL's access restricted to only one Dashboard or can it be assigned to multiple dashboard's simultaneously?
-->Session cal will allow you access N.No of Dashboards as per Section access.
2. Can the Session CAL's access restricted to any particular single user or it is open for authenticated as well as unauthenticated users?
-->It is restricted for Single user.
3. What happens if a user exceeds the defined session time?
that session will automatically assign to other users who are in Queue.
For more information go through below data.
What Are QlikView Session CALs?
Whilst both Full User and Document CALs are assigned to a user and remain with that user until they are cleared down; QlikView Session CALs are only attached to a user whilst they are in use. When a user comes to a document that they don’t have a licence for, and there is a Session CAL available, the Session CAL is allocated to them. This licence is held by that user for the duration of their session and is freed up after fifteen minutes of inactivity.
Another difference between Document CALs and Session CALs is that even when Document CALs are set to auto allocate they have to be associated with a document (as the name suggests). You can have many free Document CALs available on one document but if a user without a licence tried to open a different document, which has no free CALs, they will be denied access. Session CALs conversely are tied to the server, so this situation does not arise, if a Session CAL is available it can be used to access any document.
A quick side note on a common misuse of licences; these should never be used for security. Whilst technically a user can be denied access to a document by not having a licence, security should be left to Active Directory or Section Access (or both). A user you are keeping out of an app by not giving them a Document CAL may at a future point get this access by virtue of being given a Full CAL, for instance.
Session CALs come into their own when you have a very high number of users that use the system sporadically and in short bursts. Companies with users in many different timezones could certainly benefit. You simply need to have enough Session CALs available for the highest number of non Full CAL users that may use QlikView in any given fifteen minute period. If a user is locked out due to no CAL being available they can simply try again a bit later and may then be able to get in. By giving your high usage individuals Full CALs the number of Session CALs required is reduced.
System logs track how many licences are being used concurrently, so you can tell when you may need to add another Session CAL into the licence mix or move some users onto Full CALs.
Session CALs allow your system to flex to the usage with a minimal amount of administration time spent. Brilliant!
1. Is the session CAL's access restricted to only one Dashboard or can it be assigned to multiple dashboard's simultaneously?
-->Session cal will allow you access N.No of Dashboards as per Section access.
2. Can the Session CAL's access restricted to any particular single user or it is open for authenticated as well as unauthenticated users?
-->It is restricted for Single user.
3. What happens if a user exceeds the defined session time?
that session will automatically assign to other users who are in Queue.
For more information go through below data.
What Are QlikView Session CALs?
Whilst both Full User and Document CALs are assigned to a user and remain with that user until they are cleared down; QlikView Session CALs are only attached to a user whilst they are in use. When a user comes to a document that they don’t have a licence for, and there is a Session CAL available, the Session CAL is allocated to them. This licence is held by that user for the duration of their session and is freed up after fifteen minutes of inactivity.
Another difference between Document CALs and Session CALs is that even when Document CALs are set to auto allocate they have to be associated with a document (as the name suggests). You can have many free Document CALs available on one document but if a user without a licence tried to open a different document, which has no free CALs, they will be denied access. Session CALs conversely are tied to the server, so this situation does not arise, if a Session CAL is available it can be used to access any document.
A quick side note on a common misuse of licences; these should never be used for security. Whilst technically a user can be denied access to a document by not having a licence, security should be left to Active Directory or Section Access (or both). A user you are keeping out of an app by not giving them a Document CAL may at a future point get this access by virtue of being given a Full CAL, for instance.
Session CALs come into their own when you have a very high number of users that use the system sporadically and in short bursts. Companies with users in many different timezones could certainly benefit. You simply need to have enough Session CALs available for the highest number of non Full CAL users that may use QlikView in any given fifteen minute period. If a user is locked out due to no CAL being available they can simply try again a bit later and may then be able to get in. By giving your high usage individuals Full CALs the number of Session CALs required is reduced.
System logs track how many licences are being used concurrently, so you can tell when you may need to add another Session CAL into the licence mix or move some users onto Full CALs.
Session CALs allow your system to flex to the usage with a minimal amount of administration time spent. Brilliant!
Thank you for your responses and for the summary on Session CAL's, helped understand it better.
It is mentioned that a session CAL's can be used for any give fifteen minute period. Is the usage time restricted/fixed to 15 mins or can it be changed as per requirements?
i mean if the A user is having the session CAl, and he is using that until 4 hours it will continue .when ever the user is not using/idle without any selection then it will expires the session just like our Citrix connection.
