LabVIEW
Reading a control from LV Built application.
@sth wrote:
For some reason I can't load that code snippet. But in trying to recreate it, I can not find "ACL Create" or "Access Rights Create". I can find NI_Security but it is only a 'change password', login, or login_proxy commands. Is this a windows only functionality?
And if it is windows only do I need the corresponding .ini token on the Mac. I will try to implement that on the windows side since this is a multi-platform application.
This accessing of VI Server methods on an application is "a lot trickier than I thought" as Dennis Moore said.
I found them by searching for acl in Windows Explorer...
Sorry, I have no idea if they are there on Mac.
Search LabVIEW like a graph! 
wiebe@CARYA wrote:
I found them by searching for acl in Windows Explorer...
Sorry, I have no idea if they are there on Mac.
Where were they on Windows? I searched for both ACL and for NI_Security on the Mac and couldn't find them. They may be hidden in a LLB which would prevent finding them, but I can at least start looking in the right folder. Are they in vi.lib or one of the Application Builder libraries? I can find only the login and logout security VIs.
It may be a Windows only thing? It would be helpful if NI could confirm/deny that?
@sth wrote:
wiebe@CARYA wrote:
I found them by searching for acl in Windows Explorer...
Sorry, I have no idea if they are there on Mac.
Where were they on Windows?
vi.lib\Platform\security\user
I think these VIs are used by the Tools>Options... dialog, under VI Server>User Access. If Mac has this feature, the VIs behind it must use some SubVIs to get this done.
@Wiebe, thanks! That explains a lot. I have neither the "security" folder under the Platform folder nor the VI Server > User Access options in the preferences. Seems odd that this would be a preference that I would need to set then on the Mac platform it it can't be processed. Let me check my Windows side system.
Is that ini token needed on the Mac platform? And if not, why can I not connect to a built application?
Ahh... It is an AD thingy. And since my VM is not connected to an AD at the moment (working remotely) I can't setup any users. Of course the Mac can be connected to AD but I assume that the "security" functions are specific Windows calls to AD functionality and they didn't call the Mac funcstions for AD functionality since that is less used. Curious if the built application requires that AD functionality?
