Installed the AccessControl plugin (from the SDK’s MIPPlugins directory) on both the management client and the event server. Setup controller and doors in the management client (like in the MIPSDK manual) and configured the security roles for the relevant roles. I am however unable to view this controller in the Smart Client. All I can see when pressing the “Add Plug-In Element” on the Alarm Manager’s Toolbox is “MIP SDK Samples”, but not the controller sub items like in the manual.
To clarify, this is what the manual’s element selector looks like:
This is what my element selector looks like:
Before you can see doors in the Smart Client you need to create doors in the Management Client / Application (which also uses that plugin). Simplest explanation would be that there is no doors right now.
I believe I have a door setup in the managment client:
which is similar to the documentation:
Note that I get a slightly different “Door Information” page. Perhaps the documentation is a bit out of date?
All children (including Door) of the controller have manage/read enabled:
So it was not that simple ![]()
Questions: What versions are the MIP SDK, the XProtect test server and the Smart Client? What kind of user is this? (Basic, Windows AD or Windows workgroup?) Does it make a difference if you use a user that belongs to the Administrators role?
Unfortunatly not ![]()
The user is a Windows user. Doesn’t seem to make a difference if the user is a part of the Administrator group or the “test” group.
These are the versions:
MIP SDK 2014 (Management client reports: MIP SDK Samples, Controller v1.1.0.0)
XProtect Management Client 2014 (7.0c Build 836)
XProtect Smart Client 2014 (64-bit 9.0c Build 984)
Long time no reply..
There was a rights issue is what I have been able to find.
Please try to upgrade to the d version.
Please try to remove the controllers and door, staritng over and create them anew.
We upgraded to version d and recreated the controllers and door. However, it appears that Security Roles are broken in version d. Changing the MIP security settings doesn’t trigger the ability to save. Because of this the settings are not presistent (always unticked).
We will look into this. It could fit with some reports we have with upgraded systems.




