| Summary: To use the DocuShare mobile app successfully, your DocuShare server must have the Mobile Client Connector enabled, the Mobile Client settings must be correct, and your site must support modern HTTPS and TLS settings accepted by current Android and iOS devices. |
Prerequisites
| Requirement | Details |
| Published DocuShare URL | Use the same public or internal URL that users normally use to access DocuShare in a browser. |
| HTTPS enabled and working | The site should be reachable over HTTPS with a valid server certificate and complete certificate chain. |
| Modern TLS support | TLS 1.2 is required. TLS 1.3 is recommended where supported. |
| Modern cipher suites | Enable current ECDHE and AES-GCM cipher suites for TLS 1.2 and current TLS 1.3 cipher suites where supported. |
| Mobile Client Connector | The Mobile Client Connector must be enabled in the DocuShare Admin UI. |
| Optional print and email features | If you want mobile users to use DocuShare Print or Email, install and enable the Print and Email add-on. |
| Important: If HTTPS is not working correctly, or if the server only offers weak or outdated TLS cipher suites, the mobile app may not be able to sign in even when the Mobile Client Connector is enabled. |
Step 1 - Enable the Mobile Client Connector in DocuShare
- Sign in to DocuShare as an administrator.
- Open Administration, then go to Services and Components > Mobile Client Configuration.
- Set Enable Mobile Client Connector to Yes.
- Click Apply.
The Mobile Client Connector is included in the DocuShare software. No separate software installation is required.
| Quick result: After you click Apply, the Mobile Client Settings section should populate with the values your users will enter in the mobile app. |
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.
| Setting | What it should look like |
| Server URL | The full published DocuShare URL you want mobile users to reach. Example: https://docushare.company.com |
| Server Address | The hostname mobile users connect to. Example: docushare.company.com |
| HTTPS | On when the site uses SSL/TLS. For most production mobile deployments, this should be On. |
| Port | The same published DocuShare port. Example: 443 for HTTPS or 8443 if your site is published on a custom secure port. |
| Vendor | Use the DocuShare vendor value shown by the system. Do not replace this with your company name. |
| Service Document | The DocuShare-generated AtomPub endpoint. Example: https://docushare.company.com/ds_mobile_connector/atom/ |
Example of Completed Mobile Client Settings
| Server URL: https://docushare.company.com Server Address: docushare.company.com HTTPS: On Port: 443 Vendor: DocuShare Service Document: https://docushare.company.com/ds_mobile_connector/atom/ |
| Typical connector path: In current DocuShare deployments, the Mobile Client Connector CMIS AtomPub mapping is exposed under the DocuShare web application at /ds_mobile_connector/atom/. The exact Service Document value should still be copied from the Mobile Client Settings page rather than entered manually when possible. |
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.
| Validation tip: Run an SSL Labs test or an equivalent TLS assessment against the published DocuShare URL. A clean result with modern TLS and cipher support is the best way to confirm that the mobile app can establish a secure connection. |
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:
| Server Address: docushare.company.com HTTPS: On Port: 443 Vendor: DocuShare Service Document: https://docushare.company.com/ds_mobile_connector/atom/ |
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
- Confirm that the published DocuShare HTTPS URL opens successfully in a browser.
- Confirm that the Mobile Client Connector is enabled in the Admin UI.
- Confirm that the Mobile Client Settings page shows the expected Server Address, HTTPS, Port, Vendor, and Service Document values.
- Configure the mobile app using those same values.
- Test sign-in from both Android and iOS if both platforms are in use in your environment.
- 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:
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 |
Examples for TLS 1.3:
| TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 |