CTERA Customizations

CTERA PRODUCT
CUSTOMIZATION OPTIONS
February 2017
Version 5.5 Feature Pack 2
Copyright © 2009-2017 CTERA Networks Ltd.
All rights reserved. No part of this document may be reproduced in any form or by any means without written permission
from CTERA Networks Ltd.
Information in this document is subject to change without notice and does not represent a commitment on the part of
CTERA Networks Ltd.
CTERA, C200, C400, C800, C800+, Virtual Gateway, P1200, CloudPlug, NEXT3, Cloud Attached Storage, and Virtual Cloud
Drive are trademarks, service marks, or registered trademarks of CTERA Networks Ltd.
All other product names mentioned herein are trademarks or registered trademarks of their respective owners.
The products described in this document are protected by U.S. patents, foreign patents, or pending applications.
CONTENTS
Introduction.................................................................................................. 4
CTERA Agent and Cloud Storage Gateway Customizations ............................ 5
CTERA Agent Installation Customization Options .............................................................. 5
Local Interface Customization Options .............................................................................. 7
New User Setup Wizard Customization Options .............................................................. 10
Web Interface Customization Options ............................................................................. 13
Outlook Plugin Customization Options ............................................................................ 16
Preconfiguration Options ................................................................................................. 17
CTERA Portal Customization Guidelines ...................................................... 19

End User Portal Customization Options ........................................................................... 20
The Login Page............................................................................................................ 20
The Web Interface...................................................................................................... 24
Team Portal Administration Panel Customization Options.............................................. 26
Global Administration Control Panel Customization Options .......................................... 27
Customizing Footer Links.................................................................................................. 28
Customizing Skins ............................................................................................................. 29
Customizing CTERA Mobile.......................................................................... 30

Customizing CTERA Mobile for iOS................................................................................... 30
Customization Options ............................................................................................... 30
App Publication Guidelines ........................................................................................ 36
Customizing CTERA Mobile for Android ........................................................................... 44
Customization Options ............................................................................................... 44
App Publication Guidelines ........................................................................................ 50
CTERA Branding Customizations 3

1
INTRODUCTION
This document describes the various customization options available for CTERA products.
CTERA Agent for Windows and CTERA Cloud Storage Gateways

CTERA Agent customizations are performed by CTERA. To enable CTERA to customize your CTERA
Agent, send the following items to the sales account manager:
• A list of desired customizations
• The company logo in PNG format. The recommended size is 210x70 pixels.
• The product name
Note: When customizing the CTERA Agent, the local interface's About screen includes CTERA's
copyright.
CTERA Portal
CTERA Portal customizations are performed by your technical team, using files supplied by CTERA.
In order to customize the CTERA Portal, you need to prepare the following:
• The company logo in PNG format. The recommended size is 210x70 pixels.
You will also need to open a ticket at www.ctera.com/support and request the latest SKIN files.
CTERA Mobile
CTERA Mobile customizations can be performed for the following.
• CTERA Mobile 5.5 for Apple iOS
• CTERA Mobile 5.5 for Android

2
CTERA AGENT AND CLOUD STORAGE
GATEWAY CUSTOMIZATIONS
CTERA AGENT INSTALLATION CUSTOMIZATION OPTIONS

The following customizations can be made to the CTERA Agent Setup Wizard, which is used to install
the CTERA Agent:
• Logo
By default, the CTERA logo is displayed in the top-right corner of the wizard.
This can be changed to your company logo.

• Product name
By default, "CTERA Agent" is used as the product name.

CTERA Agent and Cloud Storage Gateway Customizations
This can be changed to the name of your product in both the window title and the screen title.
• Language
By default, the agent will use the language that is currently defined as the operating system's
active language pack. In the following example, the active language pack is English, so the wizard
is displayed in English.
If desired, the language can be preconfigured and fixed. The supported languages are: English
(United States), French, German, Italian, Portuguese (Brazil), or Spanish (Spain, International Sort).
• Default installation folder
By default, the Select Installation Folder dialog box displays the default installation path, which
includes CTERA\CTERA Agent.

The part of the path following "C:\Program Files (x86)\" can be changed to any path you prefer.
LOCAL INTERFACE CUSTOMIZATION OPTIONS

The following customizations can be made to the CTERA Agent local interface.
Note: Icons in the local interface cannot be changed.
• Logo
By default, the CTERA logo is displayed in the top-left corner of the screen.

• Background graphic
By default, CTERA's background graphic is used.

This can be changed to a graphic that suits your company's branding and color scheme.
• Default CTERA Portal
By default, the Sign in page's Server field is empty.
You can pre-fill this field with the hostname of your company's CTERA Portal.
• Default advanced settings
By default, the Advanced Settings fields are empty.

You can pre-fill these fields with your company's proxy settings.
• Product name in shell extensions
By default, the text "CTERA Agent" is displayed in the right-click menu for files and folders,
enabling users to select an item for file-level backup to the CTERA Portal.
This can be changed to the name of your product. The icon next to it can be changed, as well.
• Product tray icon menu
By default, the product tray icon menu is similar to the local interface.
The logo, fonts, font colors, action buttons, product name, language, background images, and
icons can by changed.

NEW USER SETUP WIZARD CUSTOMIZATION OPTIONS

When a new user connects the CTERA Agent to the CTERA Portal, the New User Setup Wizard is
displayed. The following customizations can be made to the wizard:
• Logo
By default, the CTERA logo is displayed in the top-left corner of the wizard.

• Icons
By default, icons are displayed on the left side of the wizard, next to Cloud Drive and Cloud Backup
in the previous screen, and next to Files to Back Up, Schedule, and Encryption in the following
screen.

These icons can be changed to custom ones.

• Fonts and Font colors
By default, the fonts and font colors are displayed as in the following screen.
Both the fonts and font colors can be customized.

• Navigation buttons
By default, the navigation buttons are displayed as in the following screen.

These buttons can be changed to custom ones.

• Language
By default, the agent will use the language that is currently defined as the operating system's
active language pack. If desired, the language can be preconfigured and fixed.

WEB INTERFACE CUSTOMIZATION OPTIONS

The following customizations can be made to the CTERA Agent Web interface:
• Logo
By default, the CTERA logo is displayed in the top-left corner of the screen.

• Product name
By default, "CTERA Agent" is displayed in the window title, in the upper-left corner of the window.

This can be changed to the name of your product.

• Restricted Agent Settings
The settings available to a Windows or MAC agent can be restricted to enabling the agent user to
perform a limited number of functions, such as manually running a backup or restoring a backup.
The following settings can be restricted:

• Select files to backup or to exclude from a backup.
• Schedule backups.
• Throttle the internet bandwidth usage.
• Default language
By default, the Web interface is displayed in English, and users can then select a different language
if desired.

The default language can be changed.

• Language options
It is possible to change the list of interface languages available in the Set Interface Language dialog
box, under Advanced > Regional Settings.
• Color scheme
To customize the agent to your company’s look and feel, you can change the color scheme from
its default settings to your preferred ones. This is true for the following:

• Fonts
• Highlighted items
• Selected items
• Action buttons
• Line separators
• Toolbars
• Icons
• Background
OUTLOOK PLUGIN CUSTOMIZATION OPTIONS

The following customizations can be made to the CTERA Outlook Plugin:
• Icons
By default, the CTERA Outlook Plugin uses the following icons:
These icons can be changed to icons of your choosing.

• Product name
By default, "Cloud Drive" is displayed in Settings dialog box as follows:
This can be changed to the name of your product.

• Attachment message color scheme
By default, the attachment message's color scheme is as follows:

This can be customized to colors of your choosing.
PRECONFIGURATION OPTIONS
It is possible to preconfigure the CTERA Agent with certain settings that will take effect immediately
upon installation. These settings include:
• SSO (Single Sign On)
Single Sign On is available when using Active Directory users. After the initial sign in, the user will
be able to log in without entering their user and password again.
• Language
By default, the language is set to English. It is possible to preconfigure the language of your choice
for all users.
• Server
By default, the Server field in the Welcome to CTERA Agent screen is empty, and the value must
be entered manually. It is possible to preconfigure this field for all users.
• Cloud Drive path
In single user mode, the CTERA Agent Cloud Drive folder is located under the following path on
Windows: volume:\ProgramData\CTERA\CTERA Agent\CloudDrive
Where volume is the volume name.
On Linux and Mac, the path is: /usr/local/cloud
In multiuser installation mode, the Cloud Drive folder is located under the user's home folder. For
example, in Windows: volume:\Users\User1\CloudDrive
By default, the user’s home folder, usually called "myfiles", is synced to this location, as well as any
other cloud folders that were configured for synchronization. It is possible to specify a different
Cloud Drive path, such as the following path on Windows:
volume:\office\storage\CloudDrive
• Mapped cloud folder
It is possible to preconfigure the CTERA Agent to set up a mapped network drive that uses
WebDAV. The CTERA Agent installer will also install a WebDAV client and will connect to the cloud
folder after connecting to the CTERA Portal.
• Online help link
By default, the Help link in the CTERA Agent Web interface leads to a help page on CTERA's
website.
It is possible to change this link, so that it leads to your own help page. The changed link will be in
the following format: your-website/help/agent/product-version/
Where:

• your-website is your website URL.

• product-version is the CTERA Agent version number.
For example, if your company website URL is http://www.example.com, then the CTERA help
link http://www.ctera.com/help/agent/5.5/ becomes
http://www.example.com/help/agent/5.5/.
Legal information link
By default, the Legal Information link leads to CTERA’s legal documents. It is possible to change
this link, so that it leads to your own legal information page.
• Hide pages
By default, all the Web interface pages are visible to the user. It is possible to hide certain pages,
and thereby prevent the user from viewing and changing the settings on those pages.
• Home page
By default, the Web interface's home page is Main > Cloud Backup. It is possible to set any other
page as the home page for all users.
If your brand requires any additional preconfiguration options, contact the CTERA team.

3
CTERA PORTAL CUSTOMIZATION GUIDELINES
When customizing the CTERA Portal follow these guidelines:
• The Login page must include the "Powered by CTERA" icon and the CTERA copyright.
• The file css.css cannot be changed; in contrast skins.css can be changed. For information,
refer to Customizing Skins.
• Mandatory references to js script are marked with a comment stating they cannot be removed.
• The login.html file must contain the controls listed in the following table.
Control ID Allowed Tags Notes

LoginCtrl div, img, button Must be contained inside login.html
ctera-ctrl div Must be contained inside login.html
• The folder structure of the base skin is as follows:
• The layout of the End User Portal's Web interface and the team portal's Administration Control
Panel cannot be changed.

CTERA Portal Customization Guidelines
END USER PORTAL CUSTOMIZATION OPTIONS
The Login Page

The Login page of the End User Portal and Control Panel can be customized by editing the
login.html file under the folder ctera_basic_skin/EndUser and the skins.css file under the
folder ctera_basic_skin/EndUser/css.
The following customizations can be made using the base skin:
• Logo
By default, the CTERA logo is displayed.

• Colors and background

By default, the CTERA color scheme and background image is used.
The interface colors, as well as the background image, can be changed to suit your company's
preference.

• Font family and font size

By default, certain font families and font sizes are used.
These can be changed as desired.

• Footer links
By default, the Support link in the footer leads to CTERA support, the Legal Information link leads
to the CTERA EULA, and the About Us link leads to CTERA’s company website.
These links can be changed as desired. For information on customizing these links in the End User
Portal, refer to Customizing Footer Links.


The End User Portal's Login page can be completely customized via the login.html file. For example:
Note: In addition to the customizations available via the base skin, you can customize the End User
Portal interface – including language, support URL, and more – via the CTERA Portal's Settings
> Virtual Portal Settings page. For information, refer to the CTERA Portal Administrator
Guides, Configuring Virtual Portals.
The Web Interface

The entire Web interface of the End User Portal and Control Panel can be customized by editing the
skins.css file under the folder ctera_basic_skin/EndUser/css.
• Logo
By default, the CTERA logo is displayed. This can be changed to your company logo.
• Colors
By default, the CTERA color scheme is used. You can change the color scheme of almost any
element in the portal interface.
By default, certain font families and font sizes are used. These can be changed as desired.

You can completely customize the End User Portal's Web interface via the skins.css file under
ctera_basic_skin/EndUser/css/.

TEAM PORTAL ADMINISTRATION PANEL CUSTOMIZATION

OPTIONS
In addition to the customizations specified in the previous chapter, the team portal Administration
Control Panel can be customized by editing the skins.css file under the folder
ctera_basic_skin/css.
• Logo
By default, the CTERA logo is displayed. This can be changed to your company logo.
• Colors and background
By default, the CTERA color scheme and background image is used. The interface colors, as well as
the background image, can be changed to suit your company's preference.
By default, certain font families and font sizes are used. These can be changed as desired.
• Footer links
By default, the Support link in the footer leads to CTERA support, the Legal Information link leads
to the CTERA EULA, and the About Us link leads to CTERA’s company website.
These links can be changed as desired. For information on customizing these links in the End User
Portal, refer to Customizing Footer Links.

The team portal Administration Control Panel can be completely customized via the skins.css file.
For example:
GLOBAL ADMINISTRATION CONTROL PANEL

CUSTOMIZATION OPTIONS
The Global Administration View and reseller portals' Administration Control Panel cannot be
customized, aside from the Help link at the bottom of the Global Administration View. For information
on customizing this link, refer to Customizing Footer Links.

Otherwise, customization is available only for the following:

• The End User Portal for end users on both team and reseller portals
• The End User Portal for team portal administrators
• The End User Control Panel for reseller portal administrators
• Invitations
• The End User Portal for guest users
CUSTOMIZING FOOTER LINKS

You can customize the following footer links:
• By default, the End User Portal's Login page contains the following links in the footer:
• A Support link that leads to CTERA support
• A Legal Information link that leads to the CTERA EULA
• An About Us link leads to CTERA’s company website
• The End User Portal's Web interface contains a Help link in the footer that leads to CTERA online
help.
• The Global Administration View contains a Help link in the footer that leads to CTERA online help.
To customize footer links:
1 Open an SSH session to the CTERA Portal server as root.
2 Connect to the CTERA Portal CLI, by running the following command: telnet localhost
Log in to the CTERA Portal CLI, by running the following command:
login Administration admin adminUserName
Where adminUserName is the admin user's name.
For example: login Administration admin admin
You are prompted to enter the administrator's password.
3 Enter the administrator's password.
4 Set up portal links:
• To set the Legal Information link for the End User Portal's Login page, run the following
command: set /settings/defaultPortalSettings/legalUrl "link"
Where link is a link to your company's legal information page.
• To set the About Us link for the End User Portal's Login page, run the following command:
set /settings/defaultPortalSettings/gui/aboutUrl "link"
Where link is a link to your company's website.
• To set the Help link for the End User Portal's Web interface, run the following command:
set /settings/defaultPortalSettings/gui/staffHelpUrl "link"
Where link is a link to your company's online help.
• To set the Help link for the Administration View, run the following command:
set /settings/defaultPortalSettings/gui/adminHelpUrl "link"
Where link is a link to your company's portal administration online help.
• To set the Help link for the End User Portal View, run the following command:

set /settings/defaultPortalSettings/gui/endUserHelpUrl "link"

Where link is a link to your company's end user online help.
Note: For all the portal links, the link must be enclosed in quotation marks and it must be an
HTTPS URL.
5 Exit the CTERA Portal CLI, by running the following command: quit
6 Restart CTERA Portal, by running the following command: ctera-portal-manage.sh restart
The changes are applied.
To set the Support link for the End User Portal's Login page, refer to the CTERA Portal Administrator
Guide, "Configuring Global Virtual Portal Settings" and "Configuring Virtual Portals".
CUSTOMIZING SKINS
To customize a skin:
1 Contact CTERA Support and request the base skin file ctera_base_skin.skin.
This is a standard CTERA skin.
2 Change the .skin suffix to .zip and extract the files to a folder.
3 To customize different css attributes, edit skins.css as desired.
4 To customize images that the base skin uses, change the image files located under
ctera_base_skin/EndUser/img, or add new ones and reference them in your code.
5 To customize the Login page, edit ctera_base_skin/EndUser/login.html as desired.
Note: Do not change the following files
• ctera_base_skin/EndUser/css/css.css or ctera_base_skin/css/css.css
• The js scripts located under ctera_base_skin/EndUser/js or ctera_base_skin/js
6 When done making customizations, edit MANIFEST.MF, and set the value of name= to the name
of your skin.
For example: name=myFirstSkin
7 Select all of the files and folders under the extracted folder and compress then into a ZIP file with
the name of your skin.
Note: Do not zip the extracted folder. Zip the contents of the extracted folder.
The name of the ZIP file must be identical to the name of the skin specified in the
MANIFEST.ME file.
8 Change the .zip suffix to .skin.
9 Upload the skin file to the CTERA Portal in the Settings > Skins page.
Note: Only a global administrator can upload a skin file to a CTERA Portal.
10 Mark the newly added skin as current.
11 Refresh the portal to apply the customizations.

4
CUSTOMIZING CTERA MOBILE
CUSTOMIZING CTERA MOBILE FOR IOS

App customizations are performed by CTERA. To enable us to customize your app, send the following
items to the sales account manager:
For an explanation of all available customizations, see Customization Options.
• The materials needed to perform the customizations.
These may include any of the following:
• The app name.
• Any graphics to be customized in PNG format.
CTERA provides the default app icon and splash page graphic in a variety of dimensions, to suit
all iOS devices. The custom app icon and splash page graphics should be in the same
dimensions and have the same file names as the CTERA graphics you received.
• The desired RGB color code of each UI component you want to customize.
• The unique device identifiers (UDID) of five iOS devices on which you intend to test the app.
Upon completing the requested customizations, CTERA will send you the app. You should then review
it and send back any comments within one month.
Once the app meets your approval, you can publish it to the Apple App Store. For guidelines on
publishing your app, see App Publication Guidelines.
Customization Options
Upon starting the branding process, you will receive a zip file that contain all of the icons, splash
screens, and images that you may want to customize to match you company’s look & feel.
Note: The following cannot be customized:
• File names
• File formats
• Files sizes (in pixels)
• Folder hierarchy
The following customizations can be made to CTERA Mobile for iOS:
• App display name
By default, "CTERA M" is used as the app name.

Customizing CTERA Mobile
This can be changed to the name of your app.

Note: If the app name exceeds 12 characters, it may be abbreviated on the device's home
screen. It is therefore recommended to take this into consideration when choosing an app
name.
• App icon
By default, the following graphic is used for app icon.
This can be changed to a graphic of your choice.

• Graphic in the splash page
By default, CTERA's graphic is used in the splash page that is displayed upon opening the app.

• Color palette
The CTERA app uses three main colors throughout its interface screens. By default, these are the
CTERA colors:
These colors can be changed to the colors of your choice.

• Login screen
By default, the CTERA cover picture is displayed in the Login screen.
The Login screen has the following customizable elements:

• Background image
• Title main color
• Back icon main color
• Continue button main color (enabled and disabled)
• The server address to which CTERA mobile should connect

The server address can be preconfigured, if desired.
If there are multiple virtual portals with different DNS suffixes, it is possible to preconfigure a
drop-down list of DNS suffixes. The user can then select the desired DNS suffix from the drop-down
list, and then enter the portal prefix in the field.
For example, if both portalA.firstportal.com and portalB.secondportal.com exist,

then the Server Address field will be replaced by of a text field where one can enter "portalA" or
"portalB", followed by a drop-down list with two options: firstportal.com and secondportal.com.
• Welcome screen
By default, the CTERA cover picture and graphics is displayed on the Welcome screen.
The Welcome screen has the following customizable elements:

• Avatar main color
• "Nice to see you" main color
• File Manager
You can customize any of the following:
• Menu icon colors
• Top navigation bar colors
• File and folder extension icons
• Side menu graphics

By default, the CTERA default graphics are displayed in the side menu.

The side menu has the following customizable elements:

• Avatar icon and full name main color
• Email color
• Background picture
• Menu icons
• Storage bar main color
• Notifications and bottom action bar
By default, the CTERA colors are displayed in the notification and bottom action bar.
The notifications and bottom action bar have the following customizable elements:
• Action icons
• Background color
• Passcode screen
By default, the CTERA interface is displayed in the passcode screen on the device.

The passcode screen has the following customizable elements:

• Logo
• Pressed and unpressed button colors
• Document provider (not signed in)
By default, the CTERA logo and colors are displayed in the document provider screen.

The document provider screen has the following customizable elements:

• Logo
• Info text
• Language modifications
By default, the app interface is displayed in the language used on the device.
The supported languages are: English, German, Spanish, Italian, and French.
CTERA supplies the language templates for all supported languages. The templates include all the
default texts and strings included in the app. You can change any of these strings to the strings of
your preference.
App Publication Guidelines

When publishing your app to the Apple App Store, follow these guidelines:
• Use the latest version of the application loader.
It should be compatible with iOS 7.
• Uploading the app must be done from a Mac machine.
• When setting up the metadata for publication:
• Be extremely careful not to mention fees or paid services.
The app is a free one, and therefore you should not charge money for it, either directly or
indirectly.
During the process of publishing the app, Apple will likely ask you questions regarding paid
services and subscriptions you sell. If they think that you are charging money for a service
related to the app, they will reject the app, since they will not consider it to be free.
If you refer to a marketing site in the app metadata, the site should not sell online services that
Apple might associate with the app (even by mistake).
The following example is text that can be used in the metadata: "This app is a free WebDAV
navigator for browsing cloud data."
• Supply Apple with a demo or test account on a reliable server.
If the server happens to be down or under maintenance at the time of testing, Apple might
reject the app.
It is recommended to include sample JPG and PDF files, in case Apple wants to test the generic
viewer.
In order to enable Apple to test the audio playback using streaming, include sample wma files.
The wma files should be relatively small (under 100KB), in order to ensure that the test is
successful.
• Do not use any trademarked terms in the app keywords or in its description. For example, do
not include terms such as "iPod", "iPhone", or "iPad".
If you need any advice on setting up the app metadata, is it recommended to consult with us
before sending the app to Apple, rather than after the app has been rejected and must be
reviewed again.
• The app is supported on iOS 5.0 and higher.
• During the process of publishing the app, you may need to supply screenshots for display in the
App Store.
The screenshots' resolution should match that of the old iPhone, iPhone 5 (640 x 1136 pixels), and
iPad.

• During the process of publishing the app, you must upload an Encryption Registration (ERN)
approval.
The CTERA app encrypts the data stored on the device, in order to prevent random access to the
user's data. Apple requires all apps that use cryptography to have an ERN approval from the
Bureau of Industry and Security (BIS); therefore, you will need to obtain an ERN approval as
described in Obtaining an ERN Approval from BISand upload it to iTunes Connect as described in
Uploading the ERN Approval to iTunes Connect.
For more information about ERN approvals, visit
http://www.bis.doc.gov/index.php/policy-guidance/encryption.
• In order to distribute the app on the App Store, you must sign it with a distribution certificate as
described in Signing the App with a Distribution Certificate.
Obtaining an ERN Approval from BIS

Note: Information on obtaining an ERN Approval is available at:
https://snapr.bis.doc.gov/snapr/docs/fieldHelp.html
To obtain an ERN approval from BIS:
1 Fill in the Encryption Registration Supplement No. 5 to Part 742 form, which was provided by
CTERA.
CTERA also supplied an example form for your reference.
2 Register your company with BIS, by filling in the following form:
https://snapr.bis.doc.gov/registration/Register.do
Once registration is complete, you will receive your Company Identification Number (CIN) via
email.
3 Browse to https://snapr.bis.doc.gov/snapr/exp/UserLoginLoad and use the CIN and
account details that you received via email to log in.
4 Click Create Work Item in the navigation pane.
The Create Work Item screen is displayed.
5 In the Type drop-down list, select Encryption Registration.

6 In the Reference Number field, type a reference number for the work item.

The reference number must be in the format AAA1111, where:

• AAA is a string composed of three capital letters.
• 1111 is a number composed of four digits.
7 Click Create.
The Edit Work Item screen is displayed.
8 Fill in the fields.
9 At the bottom of the page, click View and Manage Supporting Documents and then upload the
Encryption Registration Supplement No. 5 to Part 742 form you prepared in step 1.
Make sure the form was filled in properly before uploading it.
10 Click Save Draft.
11 Complete the registration process.
Once registration is complete, a notification is displayed informing you that your encryption
registration was accepted. An ERN also is displayed.
12 Save the approval web page, by clicking on your approved work item > View Acknowledgments
and Validations > Encryption Registration XXX accepted with ERN XXX, and then click File > Save
as in your browser's menu bar.
The acknowledgment page is downloaded to your PC.
13 Compress the web page you downloaded into a ZIP file.
Uploading the ERN Approval to iTunes Connect

To upload the ERN approval to iTunes Connect:
1 Create your new app on iTunes Connect.
2 Enter the app information and metadata.
3 Click Ready to Upload Binary.
The Export Compliance page is displayed.

4 In the Is your product designed to use cryptography or does it contain or incorporate

cryptography? field, choose Yes.
5 In the Does your product qualify for any of the exemptions provided in Category 5 part 2? field,
choose No.
For information on exemptions, visit:
http://www.bis.doc.gov/index.php/policy-guidance/encryption/identifying-
encryption-items#Three
6 In the Does your product implement encryption algorithm(s) that is(are) proprietary or yet be
accepted as standards by international standard bodies (IEEE, IETF, ITU, etc.)? field, choose No.
7 In the Does your product implement standard encryption algorithm(s) instead of or in addition
to accessing or using the encryption in iOS? field, choose No.
8 Click Choose File and browse to the zip file containing the ERN approval.
9 Click Upload File.
10 Click Save and continue the app upload process.
Signing the App with a Distribution Certificate

After receiving the final app version from CTERA, it is ready for distribution on the App Store. In order
to distribute the app, you must first sign it with a distribution certificate, as well as with the
provisioning profiles that are associated with the app App IDs.
Warning: The App IDs must be the same IDs you provided to CTERA initially. Furthermore, you
must sign the app with the distribution certificates, not the developer certificate.
Otherwise, distributing the app on the App Store will fail.

While the app provided by CTERA comes signed with a distribution certificate, it is only a temporary
certificate. It is therefore necessary to re-sign the app with your own distribution certificate. CTERA
provides a tool that enables you to easily re-sign the app with your own certificates.
Note: The tool must be run on the Mac machine from which you intend to upload the app to the App
Store.
The user running the tool must have access to the Mac machine's keychain, specifically to the
signing authority within the keychain. The Mac machine must have xcode installed as well as
the apple developers account’s official certificate and private key.
The tool supports Mac OS X v10.5 or later.
To sign the app:
1 Extract the provided iOSresign.zip file to a local folder on the Mac machine.
2 Run ./genResignInfo.sh
Usage: ./genResignInfo.sh "BundleID" "AppPrefix" “SigningCertName"
Where:
• BundleID is the bundle ID.
• AppPrefix is the app prefix taken from SigningCertName.
• SigningCertName is the signing certificate name, which can be obtained as follows: Under
KeyChain > MyCertificates, double click on iPhone Distribution, and copy the Common name
field.
Example: ./genResignInfo.sh "com.babagam.mobileWebDav" "DX8CKVFKYL"
"iPhone Distribution: BABAGAM LTD (DX8CKVFKYL)"
This generates the resignInfo.plist file for the resigning process.
3 Make sure you have four different App IDs for the process, where the main ID is the one you used
to generate resignInfo.plist.
Note: If you need to create new App ID you can do it in Apple’s member center site.
CTERA recommends providing suffixes for the three other App IDs similar to Document Picker, file
Provider and Share as in the following example.

For each App ID, the App group feature must be enabled.
4 Click Edit at the bottom of the App ID settings to enable the App group.
5 Click Edit and choose the App Group ID of the main App ID, as in the following example.

6 Create four different iOS Distribution provisioning profiles. Each profile must use a different App
ID.
• The profile that uses the main App ID.
• The names of the three others use suffixes similar to the following:
• DocumentPicker, for example CTERACloudDocumentPicker.
• FileProvider, for example CTERACloudFileProvider.
• Share, for example CTERACloudShare.

7 Download the four provisioning profiles into the local folder you created on step 1.
8 Make sure your folder has these four files:
• resignInfo.plist that was re-signed in step 2.
• CTERA_Mobile_XXX_Y.Z.W.ipa provided by CTERA Networks Ltd.
• ctera-resign-ux.sh provided by CTERA Networks Ltd.
• All four provisioning profiles
9 From the local folder you created on step 1 run the following command.
./ctera-resign-ux.sh [-i CTERA.ipa] [-p Profile] [-d Profile]
[-f Profile] [-s Profile]
Options
-i – A .ipa file provided by CTERA Networks Ltd.
-p – A provisioning profile for signing the app.
-d – A provisioning profile for signing the 'Document Picker' app extension.
-f – A provisioning profile for signing the 'File Provider' app extension.
-s – A provisioning profile for signing the 'Share' app extension.
Example:
./ctera-resign-ux.sh -i CTERA_Mobile_Company_5.7.19.ipa \
-p Company.mobileprovision \
-d CompanyDocumentPicker.mobileprovision \
-f CompanyFileProvider.mobileprovision \
-s CompanyShare.mobileprovision
10 The new re-signed file is located in the folder created in step 2.

Signed_CTERA_Mobile_XXX_Y.Z.W.ipa
This is the re-signed file to use with Application Loader.
CUSTOMIZING CTERA MOBILE FOR ANDROID

App customizations are performed by CTERA. To enable us to customize your app, send the following
items to the sales account manager:
For an explanation of all available customizations, see Customization Options.
• The materials needed to perform the customizations.
These may include any of the following:
• The app name.
• Any graphics to be customized in PNG format.
CTERA provides the default app icon graphic in a variety of dimensions, to suit all Android
devices. The custom app icon graphics should be in the same dimensions, be located in the
same drawable folder, and have the same file names as the CTERA graphics you received.
The Android splash page graphic must be in the Nine-Patch format (i.e. with the file extension
.9.png). A Nine-Patch graphic is a stretchable bitmap image, which Android automatically
resizes to accommodate the contents of the view in which it is displayed. For more information
about Nine-Patch and how to create a Nine-Patch image, visit
http://developer.android.com/guide/topics/graphics/2d-graphics.html#n
ine-patch and http://developer.android.com/tools/help/draw9patch.html.
The desired RGB color code of each UI component you want to customize.
Upon completing the requested customizations, CTERA will send you the app. You should then review
it and send back any comments within three weeks.
Once the app meets your approval, you can publish it to the Google Play store. For guidelines on
publishing your app, see App Publication Guidelines.
Customization Options
Upon starting the branding process, you will receive a zip file that contain all of the icons, splash
screens, and images that you may want to customize to match you company’s look & feel.
Note: The following cannot be customized:
• File names
• File formats
• Files sizes (in pixels)
• Folder hierarchy
The following customizations can be made to CTERA Mobile for Android:
• App display name
By default, "CTERA" is used as the app name.

This can be changed to the name of your app.

If the app name exceeds 12 characters, it may be abbreviated on the device's home screen. It is
therefore recommended to take this into consideration when choosing an app name.
• App icon
By default, the following graphic is used for app icon.

• Graphic in the splash page
By default, CTERA's graphic is used in the splash page that is displayed upon opening the app.

• Color palette
The CTERA app uses three main colors throughout its interface screens. By default, these are the

CTERA colors:
These colors can be changed to the colors of your choice.

• Login screen
By default, the CTERA cover picture is displayed in the Login screen.
The Login screen has the following customizable elements:

• Title main color
• Back icon main color
• Continue button main color (enabled and disabled)
• The server address to which CTERA mobile should connect

The server address can be preconfigured, if desired.
If there are multiple virtual portals with different DNS suffixes, it is possible to preconfigure a
drop-down list of DNS suffixes. The user can then select the desired DNS suffix from the drop-down
list, and then enter the portal prefix in the field.
For example, if both portalA.firstportal.com and portalB.secondportal.com exist,
then the Server Address field will be replaced by a text field in which one can enter "portalA" or
"portalB", followed by a drop-down list with two options: firstportal.com and secondportal.com.

• Welcome screen
By default, the CTERA cover picture and graphics is displayed on the Welcome screen.
The Welcome screen has the following customizable elements:

• Avatar main color
• "Nice to see you" main color
• File Manager
You can customize any of the following:
• Menu icon colors
• Top navigation bar colors
• File and folder extension icons
• Side menu graphics

By default, the CTERA default graphics are displayed in the side menu.

The side menu has the following customizable elements:

• Avatar icon and full name main color
• Email color
• Background picture
• Menu icons
• Storage bar main color
• Notifications and bottom action bar
By default, the CTERA colors are displayed in the notification and bottom action bar.
The notifications and bottom action bar have the following customizable elements:
• Action icons
• Background color
• Passcode screen
By default, the CTERA interface is displayed in the passcode screen on the device.

The passcode screen has the following customizable elements:

• Logo
• Pressed and unpressed button colors
• Document provider (not signed in)
By default, the CTERA logo and colors are displayed in the document provider screen.

The document provider screen has the following customizable elements:

• Logo
• Info text
• Language Modifications
By default, the app interface is displayed in the language used on the device.
The supported languages are: English, German, Spanish, Italian, and French.
CTERA supplies the language templates for all supported languages. The templates include all the
default texts and strings included in the app. You can change any of these strings to the strings of
your preference.
App Publication Guidelines

Publishing a new app on Google Play is a relatively straightforward process. Simply upload the .apk file
you received from CTERA to your developer account at
https://play.google.com/apps/publish/ and follow these guidelines:
• The app is supported on Android 2.3 and higher.
• During the process of publishing the app, you may need to supply screenshots for display in Google
Play.

CTERA Customizations

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CTERA Customizations

Uploaded by

Copyright:

Available Formats

CTERA PRODUCT

CTERA Portal Customization Guidelines ...................................................... 19

Customizing CTERA Mobile.......................................................................... 30

CTERA Branding Customizations 3

CTERA Agent for Windows and CTERA Cloud Storage Gateways

CTERA Branding Customizations 4

CTERA AGENT INSTALLATION CUSTOMIZATION OPTIONS

This can be changed to your company logo.

CTERA Branding Customizations 5

CTERA Branding Customizations 6

LOCAL INTERFACE CUSTOMIZATION OPTIONS

This can be changed to your company logo.

CTERA Branding Customizations 7

CTERA Branding Customizations 8

CTERA Branding Customizations 9

NEW USER SETUP WIZARD CUSTOMIZATION OPTIONS

This can be changed to your company logo.

CTERA Branding Customizations 10

These icons can be changed to custom ones.

Both the fonts and font colors can be customized.

CTERA Branding Customizations 11

These buttons can be changed to custom ones.

CTERA Branding Customizations 12

WEB INTERFACE CUSTOMIZATION OPTIONS

This can be changed to your company logo.

CTERA Branding Customizations 13

This can be changed to the name of your product.

The following settings can be restricted:

CTERA Branding Customizations 14

The default language can be changed.

CTERA Branding Customizations 15

OUTLOOK PLUGIN CUSTOMIZATION OPTIONS

These icons can be changed to icons of your choosing.

This can be changed to the name of your product.

CTERA Branding Customizations 16

This can be customized to colors of your choosing.

CTERA Branding Customizations 17

• your-website is your website URL.

CTERA Branding Customizations 18

Control ID Allowed Tags Notes

• The folder structure of the base skin is as follows:

CTERA Branding Customizations 19

END USER PORTAL CUSTOMIZATION OPTIONS

The Login Page

This can be changed to your company logo.

CTERA Branding Customizations 20

• Colors and background

CTERA Branding Customizations 21

• Font family and font size

These can be changed as desired.

CTERA Branding Customizations 22

CTERA Branding Customizations 23

The Web Interface

CTERA Branding Customizations 24

CTERA Branding Customizations 25

TEAM PORTAL ADMINISTRATION PANEL CUSTOMIZATION

CTERA Branding Customizations 26

GLOBAL ADMINISTRATION CONTROL PANEL

CTERA Branding Customizations 27

Otherwise, customization is available only for the following:

CUSTOMIZING FOOTER LINKS

CTERA Branding Customizations 28

set /settings/defaultPortalSettings/gui/endUserHelpUrl "link"