In order to shed some light on the real issue, please allowe me (legends, I still bow to you in any case) .
Authentication will work with any DSC under both SBC and EE QVS control. The custom directory will return a valid ID, and Windows will accept the AD Kerberos tokens.
However, authorization will have an issue with figuring out permissions to QVW files for IDs that don't really exist in AD (and as a result, neither do they exist for NTFS). Since SBE doesn't allow authorizations to be stored in DMS and managed by QV itself, nobody will be able to tell whether a Custom Directory ID is allowed to open a strictly NTFS-controlled document.
ACL's and such. It works very well though
It is very comforting to count on the support of colleagues as you both.
From what I understand, I can not use in a SBE the authority to limit the access of users to see applications using the SBE + Custom Directory?
In addition, Custom Directory for SBE is useless?
pcammaert, would you mind explaining me about your reference to ACL?
Spot on: IMHO in an SBE environment, Custom directories (any kind) are useless. Without DMS, only AD, Windows NT and Local directory DSC's serve a purpose. And the point is that QlikView Server doesn't even need a corresponding DSC for file access because AD & NTFS will do it all by themselves.
ACL's: that's just a reference to the generic concept of Access Control Lists = permission specifications by way of lists of access definitions and interdependencies. Probably way different in DMS vs NTFS.
Have a nice New Years Eve.