Closed Yoshitaka-Fukushima closed 1 month ago
I've noticed this node, "ORBNET Tools Config Node" that should not be there..
I believe this happens only when the plugin is installed after a pre-OSS version has been uninstalled.
@alexnaicuorbnet Does "Pre-OSS version" mean official version 1.8? If so, many user will do so. Uninstall v1.8 and install new version.
Pre-OSS version = 1.5.2 (the version that was not using the OSS dll) That "ORBNET Tools Config Node" is a name that was used in v1.5.2. After switching to OSS dll it was renamed to "i-PRO Active Guard".
We tested again and no. This happens when new installation and also happens when updating from v1.8.1 to this beta version @alexnaicuorbnet
Could you share a screenshot of this area when a new installation is made? @Yoshitaka-Fukushima
Could you please re-enable the TeamViewer connection? @Yoshitaka-Fukushima
@alexnaicuorbnet For our further testing, I would like to know the relationship between the selection status of the following checkboxes for watchlist access and the value specified in the OSS I/F.
Unchecked for both Allow and Deny(Default value) : Parameter "AllowxxxWacthlist" is not included? Allow : True for "AllowxxxWacthlist"? Deny : False for "AllowxxxWacthlist"?
@Yoshitaka-Fukushima In the Overall Security tab: When Allow = checked -> Role has the permission When Deny = checked -> Role doesn't have the permission When Allow = unchecked & Deny = unchecked -> Role doesn't have the permission (in this case the user can also go to the i-PRO Plugins security tab and select the permission from there)
@alexnaicuorbnet Default status for all check boxes that we added this time are unchecked in i-PRO plug-in tab. If my understanding is correct, when user update plug-in from v1.8 to v2.0, user cannot suddenly access watchlist and no attribute is shown in people/vehicle/LPR filter. Could you change default value to be checked ?
The situation is the same as what you did in v1.7 development when roles configurations were added first time.
@Yoshitaka-Fukushima Yes, that is the situation at the moment. I'll what can be done.
Fixed for v.1.9.4 All the new permissions are now set on "Allow" for all existing roles when opening the Management Client after the plugin install. Changes can be made if another configuration is preferred.
Fixed in v1.9.4
Test version: v1.9.0 on XProtect 2024R1
When checking new Roles setting from [i-PRO Plug-in]tab- [ORBNET Tools Config Node],
error is shown.
I do not the ideal behavior, but it is better to be the same as existing Roles options.
@EricBourque @alexnaicuorbnet