Skip to main content

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to versions 6 and 7.

Other available versions:

Version 5 | Version 4Link: What version am I on?

Code42 Support

Security settings reference

Who is this article for?

Code42 for EnterpriseSee product plans and features
CrashPlan for Small Business 

CrashPlan for Small Business, no.

Code42 for Enterprise, yes.

Link: Product plans and features.

This article applies to versions 6 and 7.

Other available versions:

Version 5 | Version 4Link: What version am I on?

Overview

This article is a reference guide for settings used to manage security keys, roles, LDAP, RADIUS, and single sign-on.

Keys

Security Key Settings

 

Item Description
a Require SSL to access console

Requires all web requests to use SSL. This setting is enabled by default. 

 

Every Code42 server includes a self-signed SSL certificate to support encrypted HTTPS connections. However, we recommend you import a CA-signed SSL certificate to provide additional verification to your users that the administration console is secure and is controlled by your organization. 

 

This setting impacts:

  • Access to the administration console
  • Single sign-on configuration
  • Code42 API requests

To finish enabling SSL, update the URL in the Website protocol, host, and port field to use https:// and port 4285.

b SSL Keystore Displays the file name of the Java keystore last imported.
c Import Keystore

Imports your own SSL keystore into this Code42 server.

  • The Code42 server comes with a self-signed SSL certificate.
  • The imported keystore replaces any previously installed SSL certificate.
  • The keystore is stored within the Code42 server's embedded database.
d Export Keystore Exports the currently installed SSL keystore to a file. This option is not available if the default self-signed keystore is in use.
e Reset Keystore Deletes the existing keystore and randomly generates a new self-signed SSL keystore.
f RSA Public Key Displays the public RSA key used for transport security.
g RSA Private Key Displays the private RSA key used for transport security.
h Change RSA Key Pair

Changes the RSA key pair used for transport security. This change requires a restart of the authority server to take effect.

Changing RSA keys will break server connections
Changing the RSA key pair will break any current connections between this authority server and other Code42 servers. We do not recommend it in multiple-server configurations. Restoring the connections requires manually adjusting server databases.

Roles

The Roles screen displays all user roles and the specific permissions assigned to each role. You can add, copy, and edit user roles from this screen. To assign user roles, go to the specific user's User Details > Action Menu > Edit > Roles. You may also assign roles within your existing LDAP integration settings, using the role-name script.

The SYSADMIN role has full read-write access to all orgs, users, and configuration settings. Users with the SYSADMIN role can grant any permission to themselves and to any other role or user. Other admin users with read-write access are allowed to grant only the permissions granted to themselves. When a permission is removed from an admin role, admins with the updated role can no longer grant the removed permission to any other user.

Roles

Item Description
a Roles Lists all currently available roles.
b Copy role Creates a new role with all the permissions of an existing role.
c Edit role Edits a user-created role. The standard, built-in roles cannot be edited.
d Delete role Deletes a user-created role. The standard, built-in roles cannot be deleted.
e Permissions Lists the permissions assigned to a role.
f Add Creates a new role with custom permissions.
g Users Displays the number of users currently assigned the selected role. Click to display a list of those users.

Add or edit roles

Edit roles

 

Item Description
a Role Specifies the name of the role.
b Permissions editor Determines which permissions are assigned to this role.

Role details

The available standard roles, as well as the permissions, limitations, and recommended use cases for each are described in the Roles reference.

For details about the specific permissions held by each role, review them in your administration console at Settings > Security > Roles.

LDAP

For LDAP information please see the dedicated LDAP page.

RADIUS

RADIUS Server Setup

Item Description
a Server Name Identifies the RADIUS server within your Code42 environment.
b Address

Specifies hostname or IP address and port of the RADIUS server, in the format: hostname:port

  • The word "testing" will be displayed briefly during the connection test. Wait for the test to complete before clicking Save.
  • A green checkmark and the word "Reachable" indicates successful communication.
  • A message saying "Failed" in red to the right of the Address field, indicates unsuccessful communication. Check the hostname or IP address of your RADIUS server.
c Shared Secret Sets the shared encryption key that the authority server and RADIUS server use to communicate securely.
d Attributes Sets the attribute/value pairs you want to send to the RADIUS server with each access request. Either the NAS-Identifier or NAS-IP-Address attribute/value pair is required.
e Timeout seconds Sets the timeout period for all RADIUS requests.
f Protocol

Sets the protocol used for communication with the RADIUS server:

  • CHAP - more secure method of authentication that does not transmit password in plain text.
  • PAP - less secure method of authentication that transmits password in plain text.

Single sign-on

When single sign-on (SSO) is enabled, your Code42 environment delegates all authentication and authorization to the organization's identity provider for a single source of trust. You are able to centrally control all authentication—users never enter a password into Code42 applications or the administration console. Authentication and authorization is delegated (redirected) to an identity provider, where the login is performed.

For SSO configuration instructions, see Single sign-on.

Single Sign On Settings

Item Description
a Service Provider Metadata URL Displays the URL for the authority server's SAML 2.0 metadata file. This file is used by the identity providers.
b Identify Provider(s)

Displays the configured SSO identity providers and identity federations.

c Identity federation Click to view, modify, or delete the identity federation.
d Add identity provider Click to add an identity provider from the identity federation.
e Identity provider Click to view, modify, or delete the identity provider.
f Edit this provider Click to modify the identity provider or identity federation.
g Delete this provider Click to delete the identity provider or identity federation. Identity providers cannot be deleted while they are in use by the default organization settings or specific organizations.
h Add Identity Provider or Federation Click to configure a standalone identity provider or identity federation.
i Identity Provider Details Displays a read-only view of identity provider or identity federation configuration, including metadata URL and attribute mapping. Click Edit this provider to modify the configuration.

Identity provider metadata

The following screen appears when configuring a standalone identity provider or identity federation.

Enter Identity Provider Metadata

Item Description
a Identity Provider metadata URL

Sets the URL for the standalone identity provider or identity federation metadata file. The authority server must be able to access this URL.

b Continue Click to obtain configuration values from the metadata file referenced by the URL.

Identity provider settings

The following screen appears when configuring a standalone identity provider or identity federation after you enter a metadata URL and click Continue, or when configuring an identity provider from an identity federation.

Edit Identity Provider

Item Description
a Identity Provider metadata URL / Choose identity provider
  • For standalone identity providers and identity federations, Identity Provider metadata URL contains the URL for the identity provider or identity federation metadata file. The authority server must be able to access this URL.
  • For identity providers in a federation, Choose identity provider lists the identity providers in the federation. Select an identity provider from the list.
b Update Click to check the metadata file referenced by the URL for changes.
c Display name Sets the name of your organization's SSO identity provider. This is a descriptive label and the text entered here is displayed to the user on the sign-in screen of the Code42 applications and administration console.
d Path to identify provider display name
(federations only)

Sets the path to identity provider display names in the identity federation metadata XML file.
Example path: //mdui:DisplayName

  • When the path is configured, display names for identity providers are pulled from the federation metadata XML file and presented to users as a choice when they sign in using SSO.

  • When the path is not configured, the full paths for the identity providers are displayed.

e Use default mapping Enables or disables default mapping between Code42 platform username attributes and SSO username attributes.
f Username

Maps Code42 platform usernames to the SSO name identifier or a custom attribute.

  • Select Use nameId to use the SSO name identifier.

  • Select Use Attribute tag to enter a custom SSO attribute.

g Email Maps Code42 platform user email addresses to an SSO attribute.
h First name Maps Code42 platform user first names to an SSO attribute.
i Last name Maps Code42 platform user last names to an SSO attribute.

Storage server security settings

Viewing the Security settings from the administration console of a storage server presents a limited number of options for SSL.

Storage server security settings

Item   Description
a Require SSL to access console

Every Code42 server includes a self-signed SSL certificate to support encrypted HTTPS connections. However, we recommend you import a CA-signed SSL certificate to provide additional verification to your users that the administration console is secure and is controlled by your organization. 

 

To finish enabling SSL, update the URL in the Website protocol, host, and port field to use https:// and port 4285.

b SSL Keystore

Java keystore that contains your key materials.

c Import Keystore

Imports your own SSL keystore into this Code42 server. The imported keystore replaces any previously installed SSL certificate. The Code42 server comes with a self-signed SSL certificate. The keystore is stored within the Code42 server's embedded database.

d Export Keystore

Exports the currently installed SSL keystore to a file.

e Reset Keystore

Deletes existing keystore and randomly generates a new SSL keystore.