The Cloud Administrator can update the SaaS Apps/Endpoints settings once the users are provisioned.
Procedure
On the Endpoint/ SaaS Apps workload page, go to the settings icon.
Select Endpoints & SaaS Apps settings and update the settings for the below components.
Update User Password Settings
The Password Policy is enabled by default with mandatory settings that allow you to govern the password creation and control the password lifecycle.
Expand to see a glimpse
Click the edit button and update the below fields:
Field | Description |
Enable Password policy | Select this checkbox to enable the Password Policy for the users. Additional fields appear. |
Enforce Strong Password | Select this checkbox to enforce a strong Password Policy.
|
Cannot reset password to last | Enter the value to restrict users from setting passwords similar to previous ones. Set 0 for no limitations.
π Note
For inSync GovCloud environment, the users cannot reset their password to the last 24 passwords by default. |
Minimum lifetime for password | Type the number of days you want a password to be used before the user can change it. The possible value range is between 1-60 days. Set the Minimum lifetime for password age to a value of 1 day. Setting |
Max. invalid login attempts | Enter the maximum number of login attempts. The user's account is locked after invalid login attempts are exceeded. |
Password expire after every | Type the number of days after which the user must reset the password. The recommended value range is 1 to 60 days.
π Note
|
Configure Network Settings
You can allow or restrict inSync Client to back up the user data over specific networks. Similarly, you can define a unique string name for Druva Cloud to identify the network you want to allow/block.
Expand to see a glimpse
Click the edit button and update below fields:
Field | Description |
Allowed network for backup | Add the network you want to allow backup data.
π Note
Use a semicolon with space to add multiple networks. Example: OfficeNetwork;SecuredLAN;CORP |
Restrict backup on any other network | Select this checkbox if you do not want to backup user data on any network other than the allowed networks |
Restricted networks for backup | Add the network you want to restrict backup data.
π Note
Use a semicolon with space to add multiple networks. Example: OfficeNetwork;SecuredLAN;CORP |
The following table lists the guidelines to set unique string names on Windows and macOS devices.
Windows | macOS |
|
|
Customize Email Template
You can customize the email template sent to users.
Expand to see a glimpse
Click the Edit button to update the below fields:
Field | Description |
Reply to | The reply-to email address of the Druva Cloud.
π Note
By default, this field contains the email id of the first Cloud administrator. |
Sender name | The sender name for emails sent by the server. |
Signature | The signature that appears on emails sent by the server. |
Enable Cloud Key Management
The Cloud Key Management feature is a secured mechanism to back up the SaaS Apps data and is an alternative method to the AD/LDAP Connector-based deployment.
Once you receive the confirmation email from Support about the activation of the Cloud Key Management feature for your account, you can enable it by selecting the Enable option. For more information, see Configure Cloud Key Management.
Add and manage Connectors
The AD/LDAP Connector is an agent used to install on a Windows device or server within your organization's network.
You need the Connector:
When using Active Directory (AD) or Lightweight Directory Access Protocol (LDAP) to import and manage new users in Druva.
When you want to protect Cloud Apps Office 365 and G-Suite data for your users, and you do NOT have:
A user endpoint device (desktop or laptop) configured for backup in Druva.
The Cloud Key Management feature is enabled.
The following table lists the actions you can perform in the Connectors tab.
Action | Description |
Add Connector | Add a new inSync Connector in your environment. For more information, see Install or upgrade AD Connector. |
Delete Connector | Delete an existing inSync Connector in your environment. For more information, see Delete AD Connector. |
Get Registration Key | Generate a new registration key to register inSync Connector in your environment.
π‘ Tip
Do not regenerate the registration key after the inSync Connector is registered. If you regenerate the key, the existing registration key is deactivated. |
β