Site Manager can be configured to allow different users on the Site Manager server or a Windows Active Directory Domain to login to Site Manager.
By default members of the Administrators group on the Site Manager server and members of Domain Administrators on the Site Manager server's domain can login. Additional domains and permissions can be configured as described below.
Login providers serve as the interface between Site Manager and an authentication resource. There is a unique login provider for each authentication resource so that permissions for each resource can be managed independently by configuring the associated provider. Three types of Login Provider currently exist:
|Login Provider Type||Authentication Resource||Included by Default||Notes|
|Server Local||User Account Control||Yes||Authenticates local users. Local administrator accounts will always have permission to access Site Manager.|
|Primary Server Domain||Active Directory||Yes (if the Site Manager server is joined to a domain)|
Authenticates users on the domain the Site Manager server is joined to. It is created automatically and can not be removed by the user. Domain Administrators can log in using this provider.
If the server is moved from its domain then the provider will be converted to a Domain provider. A new Primary Server Domain provider will be created when Site Manager upon reconnecting to a domain.
|Secondary Server Domain||Active Directory||Yes (if the Site Manager server is joined to a domain in a forest)|
Authenticates users on domains within the forest the Site Manager server is joined to. It is created automatically and can not be removed.
If the server is moved from its domain then the provider will be converted to a Domain provider. A new set of Secondary Server Domain providers will be created on start up.
|Domain||Active Directory||No||This provider interfaces with Active Directory domains other than that which the Site Manager server is connected to.|
Active Directory compatibility
Site Manager must connect with a Domain Controller which supports LDAP v3 for permissions to be set for accounts on the Domain. LDAP over SSL will be used if available.
Managing Login Providers
Disabling Domain Forest Searching
Site Manager automatically creates Local, Primary Server Domain and Secondary Server Domain providers on startup.
Users can stop Site Manager creating domain providers by setting the registry value "Configure default providers" in the key "HKEY_LOCAL_MACHINE\SOFTWARE\Macrium\Site Manager" to 0. This will prevent Site Manager from creating any providers except the primary domain and local computer providers.
While the automatic providers should cater for most needs, custom domain providers can be created to connect to domains outside of the forest the Site Manager server is in. Beware that members of authorized groups can only access Site Manager if they are on the same domain as the group. This differs from the automatic domain providers which support cross domain authorization.
All providers are listed within the provider manager dialog. Providers can be configured or removed by clicking the respective buttons in the table. New providers can be created by clicking the Add button, which opens the a dialog to configure a new Domain provider.
A Domain provider can be configured with the following fields:
|Name||A friendly name which is displayed to users. If no name is provider then the provider will be named after the domain it is associated with.|
The host name of a domain controller. This can be in the form of a DNS-style name, a NetBIOS address or an IP address.
Site Manager will communicate with the domain controller using LDAP. To use custom ports (other than the default of 389 or 636) specify the domain controller in the hostname:port format.
|Username||The username of an account on the domain. The credentials of this account will be used to perform any lookups against the LDAP server.|
|Password||The password of the account specified by the username entered in the previous field.|
|Display Order Priority||The order the provider will appear in dropdown lists like on the login page and the permissions modal. There is also an option to hide the provider from lists other than the table in the provider manager which may be useful if there are unused automatically generated providers.|
After clicking "Save", Site Manager will check the validity of the configuration. If a provider can be created then the configuration is saved and a provider is added to the list of providers in the previous window. Otherwise, the an error message will appear explaining the problem.
Configuring Role Based Permissions
Next to the Manage Provider button on the security settings page is the Manage Permissions button. Clicking this button will open the permissions management window.
Permissions are configured separately for each provider. Select the correct provider from the dropdown before configuring permissions.
A table listing the active permissions is below the provider selection field. Here the names of authorized users and groups are displayed. All members of an authorized group are given the permissions of that group (membership is applied transitively). Permissions can be deleted by clicking the Remove button. Click Configure to add permissions. Changes to permissions can be discarded by clicking cancel.
The structure of the directory is navigable through the tree on the left, which shows the folders and Organizational Units which have been configured on the domain. On the right is a table listing the users and groups in the selected folder. Rows can be selected to add corresponding permissions when the Add button is pressed.
All users and groups newly added to the active permissions listing are defaulted with the 'Viewer' role, this role is the lowest form of access granted by Site Manager. To increase a users or groups access further, select Edit from the Role column to access the role editor.
The role editor displays all role options available for selection. Select the roles required for the user or group and apply changed roles by clicking the Save button. Roles can be combined where required, selecting all the non-administrator roles is equivalent to granting the administrator role to Site Manager.
|Administrator||Grants full administrative access to the Site Manager user.|
|Standard User (Viewer)||Grants minimum access to the Site Manager user. A user with this role can view the majority of information available in Site Manager, but can't make changes beyond configuring their own instance of the dashboard and table layouts. The repository browser and verification pages are unavailable to the user.|
|Backup Operator||Grants the same access as a 'Standard User' to Site Manager, but the user can enable or disable predefined backup plans, start, stop or pause backups, start or stop remote syncs, access the repository browser (without access to backup contents) and verify backups.|
|Restore Operator||Grants the same access as a 'Standard User' to Site Manager, but the user can perform remote restores, generate and download rescue media, access the repository browser (and open backups) and verify backups.|
Grants the same access as a backup and restore operator to Site Manager, but the user can configure backup plans, definitions, schedules, repositories, remote sync's, agent tags along with access to the repository browser (full access, including deletion) and full access to manage agents (add, remove, remote install, upgrade and perform maintenance actions including reboot agent, reset VSS and resync logs).
Grants the same access as a 'Standard User' to Site Manager, but the user can configure server settings, configure repositories, access the repository browser (view listings only), manage agent licensing, perform agent maintenance actions (reboot agent, reset VSS and resync logs), generate rescue media and install server updates.