How to Configure the DocuShare Mobile App and Mobile Client Connector

Prerequisites

Step 1 - Enable the Mobile Client Connector in DocuShare

1. Sign in to DocuShare as an administrator.
2. Open Administration, then go to Services and Components > Mobile Client Configuration.
3. Set Enable Mobile Client Connector to Yes.
4. Click Apply.

The Mobile Client Connector is included in the DocuShare software. No separate software installation is required.

Step 2 - Verify the Mobile Client Connector Settings

After the connector is enabled, review the Mobile Client Settings shown on the Mobile Client Configuration page. These are the same values users need when they configure the mobile app.

If the values are wrong, enter your DocuShare site URL in the Server URL field, click Set, review the updated settings, and then click Apply to save them.

Example of Completed Mobile Client Settings

Step 3 - Confirm HTTPS and Certificate Readiness

• Open the published DocuShare URL in a browser and confirm the site loads without certificate warnings.
• Use the same DNS name in the mobile app that is presented in the server certificate.
• If your site is published through IIS, Apache, or another reverse proxy, verify that the published HTTPS URL is the same URL you use in the Mobile Client Configuration page.
• If your site uses a private or internal certificate authority, make sure mobile devices trust that CA.

Step 4 - Confirm TLS and Cipher Requirements

Modern Android and iOS devices require current TLS settings. Legacy-only TLS configurations can prevent the mobile app from establishing a secure connection.

For most environments, focus on these checks:

• Enable TLS 1.2.
• Enable TLS 1.3 if your server platform supports it.
• Disable TLS 1.0 and TLS 1.1.
• Use modern cipher suites such as ECDHE plus AES-GCM for TLS 1.2, and standard TLS 1.3 cipher suites where supported.
• Disable weak or deprecated cipher families such as RC4, MD5-based suites, and 3DES / TDEA.

If you need example cipher suite names for server review, see Appendix A at the end of this document.

Step 5 - Configure the Mobile App

When adding the DocuShare account in the mobile app, copy the values from the Mobile Client Settings page in DocuShare.

A simple example is shown below:

If your site uses a different secure port, use that port instead. For example, if your published URL is https://docushare.company.com:8443, the Port value should be 8443 and the Service Document should use the same address and port.

If you use the wrong URL, a non-secure URL, or values from an older site configuration, the app may fail to sign in or may not reach the DocuShare repository correctly.

Step 6 - Validate the Configuration

1. Confirm that the published DocuShare HTTPS URL opens successfully in a browser.
2. Confirm that the Mobile Client Connector is enabled in the Admin UI.
3. Confirm that the Mobile Client Settings page shows the expected Server Address, HTTPS, Port, Vendor, and Service Document values.
4. Configure the mobile app using those same values.
5. Test sign-in from both Android and iOS if both platforms are in use in your environment.
6. If the connection fails, review ds_mobile_connector.log and ds_mobile_connector.log.1 in the tomcat\logs folder of the DocuShare installation.

Optional Features

• DocuShare Print and Email features in the mobile app require the DocuShare Print and Email add-on to be installed and enabled.
• If you want the app to display DocuShare in another language, install and configure the appropriate DocuShare language pack and make sure the mobile device is set to that language.

Troubleshooting Checklist

• The Mobile Client Connector is enabled, but the app still cannot sign in: verify HTTPS, TLS version, and cipher support first.
• The settings page shows incorrect values: enter the correct published DocuShare URL in Server URL, click Set, then click Apply.
• The app can reach the server but fails the secure handshake: check for TLS 1.0 / 1.1, RC4, 3DES, or other legacy-only cipher configuration on the server or proxy.
• The connector was working before a server or proxy change: recheck the published hostname, certificate, and Mobile Client Settings values.

Appendix A - Example Modern Cipher Suites

Use this appendix only if your infrastructure team needs example suite names while reviewing server or proxy configuration. The exact list available on your platform may differ.

Examples for TLS 1.2:

Examples for TLS 1.3: