Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I´m facing a problem trying to enable some users to see their documents into Access Point. I want that users listed under "Section Access" should be able to see (and open) documents in AP.
Our enviroment
Script sample:
SECTION ACCESS;
LOAD * INLINE [
ACCESS, NTNAME
ADMIN, SRVQLIKVIEW01\qlikview
ADMIN, SRVQLIKVIEW01\qvapp
USER, CUSTOM\CLEVER.ANJOS
];
Issue:
CUSTOM\CLEVER.ANJOS does not see any document
Any hint or help?
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.
Peter
Leaving the section access aside for a moment (assuming it has been disabled), how do you want to give your custom users authorization to open the QVW in accesspoint without DMS?
And leaving DMS issue aside, I think you can't use NTNAME with a custom user. You would need to use USERID and PASSWORD (yes, I think you need to state the password, so user would need to login again).
Great double response, Stefan. And entirely correct (as expected )
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
'night,
Peter
(It's still a bit "weird" for Q in L, SE to allow configuration of Custom Directories in an SBE environment without warning the user/admin about the possible issues. And the Docs remain silent about this conflict as well. Marketing? Still a mystery to tech guys like me...)
swuehl, you´re correct,
Checking here a Custom User can´t see any doc.
DMS is disabled by license, can´t change that
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.
Peter
Thanks a lot