HOBCOM Universal Server Basic Training course

Our team Instructor Erwin Palma Account Manager Alexa Kaiser

HOBCOM Universal Server (HCU) 19.05.2019 HOBLink Mobile One Solution - Two Components HOBLink Mobile consists of two components: HOBLink Mobile application for mobile devices HOBCOM Universal Server (HCU) central server component HOBCOM Universal Server (HCU Server) is the server component of HOBLink Mobile, a solution that provides secure remote access to e-mails, calendar entries, contacts and notes. With HOBLink Mobile, an app for Apple iOS and Android devices, access to centrally stored enterprise resources at any time and from anywhere is easy and secure. Enterprises profit from more effective business processes and employees are able to access their corporate Microsoft Outlook accounts from any mobile device (iOS and Android).

HOBCOM Universal Server 19.05.2019 HOBCOM Universal Server Direct Connection Direct communication between HCU Server and HOBLink Mobile. This is always encrypted with AES (128-bit) encryption. A dedicated HCU protocol developed by HOB is used for communication between the HOBLink Mobile device and HCU Server. The advantage of using direct communication is that it is easy to use and offers security.

HOBCOM Universal Server 19.05.2019 HOBCOM Universal Server Secure Connection Communication between HCU Server and HOBLink Mobile over the HOB RD VPN WebSecureProxy (HOB WSP). HOB RD VPN is a software solution that is specially designed to give you secure remote access over the Internet to the resources in your corporate network. HOB WSP is the central server component of HOB RD VPN. The advantage of using communication over the HOB WSP is that it offers an even higher level of security requiring certificates. In addition, it is encrypted with SSL. NOTE: HOB WSP is not included in the HOBLink Mobile solution – it can be obtained at an additional cost.

HOBCOM Universal Client 19.05.2019 HOBCOM Universal Client Authentication Authentication for a direct connection to the HCU Server is carried out through a username and password combination. There are two types of authentication: Local Users are managed by the HCU Server. A separate password can be chosen for HOBLink Mobile and HCU Server. Login and creating users has to be done on the HCU Server side. LDAP HCU Server sends a request to the LDAP server and asks if the domain password is correct.

System Requirements Server – Operating Systems supported 19.05.2019 System Requirements Server – Operating Systems supported HCU Server runs on the following operating systems: Microsoft Windows Server 2008 R2 Microsoft Windows Server 2012 Microsoft Windows Server 2012 R2 Microsoft Windows Server 2016 HOBCOM Universal Server (Admin guide page 8) HOB recommends using the HCU Server without virtualization on a multi-core CPU.

System Requirements Server - Hadware 19.05.2019 System Requirements Server - Hadware The minimum hardware requirements are: CPU – minimum: 1 GHz, recommended: 2 GHz RAM – for up to 100 users: at least 512 MB; for more than 100 users: at least 1 MB is additionally required for each user, recommended: 2 MB Network card – required; recommended: 100 MBit/s HDD – minimum: 500 MB hard disk space HOBCOM Universal Server (Admin guide page 8)

System Requirements Network - Microsoft Exchange Server 19.05.2019 System Requirements Network - Microsoft Exchange Server From version 2010 and later, Exchange Web Services must be activated. Push notifications require Microsoft Exchange 2010 or later.

System Requirements Client side - HOBLink Mobile 19.05.2019 System Requirements Client side - HOBLink Mobile iOS 8 or newer Android 4.0.3 or newest iPhone iPod Touch iPad HOBCOM Universal Server (Admin guide page 8) Handy Tablet

System Requirements Ports 19.05.2019 HOBCOM Universal Server (Admin guide page 8) Ports The HCU Server listens on the following configurable ports: 5099 – for user access via HOBLink Mobile clients 8080 – for Web Administration via HTTPS 8081 – for Web Administration via HTTP The HCU Server connects to the APNS via the following port: 2195 – for Apple Push Notification Service

HOBLink Secure Module HOBLink Security Units 19.05.2019 HOBLink Security Manager Admin Guide Page 38 The HOBLink Security Manager 3, files for the server and the client. These files are referred to in the following as “HL Security Units.” An HL Security Unit includes the following files: The *.cfg file: includes all information about the configuration of the SSL-encrypted connection you selected. The *.cdb file: is a certificate database and contains all public and private keys required for this server or client. The *.pwd file: contains the password with which *.cfg and *.cdb file are protected. This file is generated only if you expressly specify it. If this file is present, the password prompt for the user during connection setup is omitted. Every server or client requires an HL Security Unit. The files of the server HL Security Unit must have the name prefix hserver.*, the files of the client HL Security Unit must have the name prefix hclient.*.

HOBLink Secure Module HOBLink Security Units 19.05.2019 hclient.* means (hclient.pwd, hclient.cfg and hclient.cdb) 1- Connection to MS-Exchange Import the SSL certificates for Microsoft Exchange into the SSL configuration of the HCU Server if it is needed .The default location of the hclient files for connecting to the Microsoft Exchange is ./sslsettings/hclient.* 2- Connection to APNS The preconfigured address of the APNS is gateway.push.apple.com and it uses port 2195. The client certificate is stored by default at .\sslsettings\APNS\hclient.* . This certificate can only be created by HOB. It is valid for approximately one year and must be renewed by HOB. 3- HOB RD VPN The path to the SSL certificates is the complete HOB RD VPN address followed by the file path: https://rdvpn.mycompany.com/public/lib/sslpublic/hclient.*

Bibliography A. (2017, November 13). APNs Overview. Retrieved February 28, 2018, from https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNot ificationsPG/APNSOverview.html#//apple_ref/doc/uid/TP40008194-CH8-SW1 [Accessed 28 Feb. 2018]. Vesza, J. (2018). Push Notifications Tutorial: Getting Started. [online] Ray Wenderlich. Available at: https://www.raywenderlich.com/156966/push-notifications-tutorial-getting-started [Accessed 28 Feb. 2018].

19.05.2019 Contact Information HOB GmbH & Co. KG Schwadermuehlstraße 3 90556 Cadolzburg GERMANY +1 646 465 7649 +49 9103 715 3715 intsales@hobsoft.com www.hobsoft.com

Legal Notice HOB GmbH & CO. KG. KG Schwadermuehlstr. 3 90556 Cadolzburg Represented by: Klaus Brandstätter, Zoran Adamovic Contact: Phone: 0049-91037150 Fax: 0049-9103715271 E-mail: marketing@hob.de Register of Companies: Entered in the Registry of Companies, Registry Court: Amtsgericht Fürth, Registration Number: HRA 5180 Tax ID: Sales Tax Identification Number according to Section 27a Sales Tax Act: DE 132 747 002 Responsible for content according to Section 55 Paragraph 2 Interstate Broadcasting Agreement: Klaus Brandstätter, Zoran Adamovic, Schwadermuehlstr. 3, 90556 Cadolzburg References for all images and graphics used: All pictures and images included in this publication to which HOB does not hold the copyright must be credited to the current copyright holders. See section Picture Sources   Disclaimer: Liability for content The contents of this publication were created with great care and diligence. While we keep it as up-to-date as practicable, we cannot take any responsibility for the accuracy and completeness of the contents of this publication. As a service provider we are responsible for our own content in this publication under the general laws according to Section 7 paragraph 1 of the TMG. According to Chapters 8 to 10 of the TMG we are not obliged as a service provider to monitor transmitted or stored information not created by us, or to investigate circumstances that indicate illegal activity. Obligations to remove or block the use of information under the general laws remain unaffected. Liability is only possible however from the date of a specific infringement being made known to us. Upon notification of such violations, the content will be removed immediately. Liability for links This publication may contain links to external websites over which we have no control. Therefore we can not accept any responsibility for their content. The respective provider or operator of the website pages to which there are links is always responsible for the content of the linked pages. The linked sites were checked at the time of linking for possible violations of the law. At the time the link was created in this publication, no illegal or harmful contents had been identified. A continuous and on-going examination of the linked pages is unreasonable without concrete evidence of a violation. Upon notification of any violations, such links will be removed immediately. Copyright The contents and works on these pages created by the author are subject to German copyright law. Reproducing, copying, modifying, adapting, distributing or any kind of exploiting of this material outside the realms of copyright require the prior written consent of the respective author or creator. The downloading of, and making copies of, these materials is only permitted for private, non-commercial use. Where contents of this publication have not been created by the author, the copyright of the third parties responsible for these contents shall be upheld. In particular any contents created by a third party are marked as such. If you become aware of any copyright infringement within this publication, we kindly ask to be provided with this information. Upon notification of any such violation, the concerned content will be removed immediately.