For users and access rights. If you use windows authentication for example (the most common option), you need to connect QlikView to the domain controller so that authentication can take place.
It's even simpler: the DSC is used by almost every other QV service to lookup information about users (group membership, emails, UID's, FullNames and stuff). Authentication has happened earlier on, and on average isn't done by the QV services at all but by Windows.
There is a good explanation of the DSC functions in the QlikView Server Reference Manual - Ch 6.5
If i am not wrong then after authentication , there comes authorisation. So here comes DSC to see whether a person is authorise to see a particular qvw or not. Is it so ??
If i am not wrong then after authentication , there comes authorisation. So here comes DSC to see whether a person is authorise to see a particular qvw or not. Is it so ??
Not really. Authorizations are either stored in NTFS ACLs or in .pgo files. Access may also be regulated by the SectionAccess NTNAME field if you do use SectionAccess. The QVS will simply look up the ID of the person at the door in these sources, and grant access or not.
IMHO, DSC has nothing to do with authorizations either.
Expand the QMC->System->Setup->Directory Service Connectors->DSC@servername tree. Those are the different repositories that the QV DSC can query through a properly configured DSP. Click Help at the top right for details about each different Directory Service Provider.
AFAIK a SBE version of QlikView server can only configure Active and local directories.
