1.Login under df-admin (DF “SuperAdmin” role)
Here you will see almost all the info that DF fetches from Milestone
2.Login by current AtiveDirectory/regular Windows user
Login to Windows by AD user.
Login to DF by “Current Windows user” option.
You will see only cameras and business logics, that you have permissions for.
Cameras – from Milestone permissions.
Business logics – from DF SuperAdmin Permissions (df-admin by default).
3. Login by non-current AtiveDirectory/regular Windows user
Launch browser in incognito mode.
Select Current Windows user option on login page and press LOGIN button.
Enter in “Sign in” form Windows’ user credentials.
Active Directory username example:
user1@ad.ff-group.local
user1 – user name
ad.ff-group.local – AD domain
In some cases, press F5 (refresh page) so all data fetches from Milestone.
If you want to login by another non-current Windows user, close Incognito browser, launch it again and login by another user.
In case of regular Windows login (without ActiveDirectory) it’s may be with or without domain name.
4. Auto-login in Smart client (current Windows user only)
When you start SmartClient application you will automatically to DF via current Windows user, in regardless of the SmartClient user.
5. Fetching roles from Milestone to Data Factory
6. Business logics and events flow federalization
7. Federalization Business logics set and settings
7.1. Requirements
1.Bussines logic should have different levels of permissions:
a. Owner/administrator level - can configure groups and analytic event parameters. + all other operational operations.
b. Operator - can add/modify/delete license plates in existing groups + see/search/export events;
(he should not be able to add/modify/delete groups or analytic events parameters).
2.Business logic should be visible and manageable based on access rights - for example a regional dispatcher can see only the bussines logic for his region,
but a central dispatcher should be able to see all the business logics for which he has rights (all the regions).
For each user/groups we should be able to select the permissions for each business logic.
7.2. Business logics set
1.Business logics, restricted by Milestone’s permissions (by cameras set)
a.List and Alerts_2.1.12 Dispatcher.blc – only cameras’ events receiving restrictions according to Milestone’s permissions .
No ability to modify analytic events parameters.
b.List and Alerts_2.1.12 Operator.blc – can add/modify/delete license plates to existing groups, have cameras’ events receiving restrictions according to Milestone’s permissions.
No ability to modify analytic events parameters.
2.List and Alerts_2.1.12 Central.blc – no restrictions. At all.
All other requirements may be done by combination of business-logics above and User Management (permissions) system
Single DataFactory role per 1 region
Group name (of license plates list) must be unique at all
7.3. Users and Roles scheme
7.4. Setting steps
1.Add business logics to DF (List and Alerts_2.1.12 Central.blc, List and Alerts_2.1.12 Dispatcher.blc, List and Alerts_2.1.12 Operator.blc)
2.Connect to Milestone under SuperAdmin user (df-admin by default), via Basic user with Administrator’s Role in Milestone.
Refresh DF SETTINGS page.
3.Add DF Role and set list of appropriate set of Milestone’s roles.
4.Assign Business logic to the appropriate DF Role.
5.Each user has to create Business-logic instance and activate it.