- BlackBerry Docs service
- Steps to configure the Docs service in an on-premises environment
- Configure the database connection for the BlackBerry Docs service
- Configure a web proxy server for the Docs service
- Configure the Docs network and security settings
- Storage services
- Managing Repositories in an on-premises environment
- Configuring repositories in an on-premises environment
- Steps to define admin-defined repositories and repository lists
- Enable user-defined repository permissions
- Configuring Docs for Rights Management Services
- Using the Docs Self-Service web console
- Configuring support for Microsoft SharePoint Online and Microsoft OneDrive for Business
- In a BlackBerry UEM environment, add an app server hosting the Docs service to a BlackBerry Dynamics connectivity profile
- Auditing the Docs service
- Steps to configure the Docs service in a BlackBerry UEM Cloud environment
- Enable the Docs service
- Configure the Docs service settings
- Create a trusted connection between the Docs service and Microsoft SharePoint
- Managing repositories in a BlackBerry UEM Cloud environment
- Configuring the Docs instance for high availability
- Next steps to configure BEMS
- Appendix: File types supported by the BlackBerry Docs service
- Appendix: Windows Folder Redirection (Native)
- Appendix: Local Folder Synchronization – Offline Folders (Native)
- Appendix: Supported Microsoft Office Web Apps and Office Online Server file types
- BlackBerry Docs
- BlackBerry Enterprise Mobility Server 3.8
- Configuring the BlackBerry Docs service
- Steps to configure the Docs service in an on-premises environment
- Configure the Docs network and security settings
- Configuring Kerberos constrained delegation for the Docs service
- Create Service Principal Names
Create Service Principal Names
- Create a Service Principal Name (SPN) for each web application that needs to be shared as follows:setspn –S HTTP/SPHOST:PORT <domain>\AppPoolUser setspn –S HTTP/SPHOST.FQDN:PORT <domain>\AppPoolUser setspn –S HTTP/SPHOST <domain>\AppPoolUser setspn –S HTTP/SPHOST.FQDN <domain>\AppPoolUserIf the port is a default port, such as 80 or 443, omit the commands that include port above. Some of the lines only require a host name while others require a fully qualified host name. If the application pool identity is for a built-in user such as Network Service, then specify the host name as shown below instead of <domain>\AppPoolUser.setspn –S HTTP/SPHOST:PORT <domain>\SPHOST setspn –S HTTP/SPHOST.FQDN:PORT <domain>\SPHOST setspn –S HTTP/SPHOST <domain>\SPHOST setspn –S HTTP/SPHOST.FQDN <domain>\SPHOSTIf you use SSL, the SPN must refer to HTTP instead of HTTPS.