LearningSpace is a web application that is accessed by a web browser on the client's computers. To secure the data travelling between the LearningSpace system and the client's browser, the otherwise unsecure HTTP traffic needs to be encrypted using strong SSL certificates, resulting in HTTPS traffic.
For SSL secure access setup, an SSL certificate has to be acquired. |
The Intercom functionality of LearningSpace requires the web browser to have access to the microphone of the client PC, which in turn requires a secure HTTPS connection to the LearningSpace server. It is the responsibility of the end-user institution to provide the SSL certificate.
Healthcare strongly recommends installing a valid SSL certificate for use in LearningSpace. The securely encrypted HTTPS traffic will minimize the risks that are inherent to applications connected to the Internet. |
SSL certificates create a foundation of trust by establishing a secure connection. To assure visitors their connection is secure, browsers provide special visual cues that we call EV indicators: anything from a green padlock to branded URL bar. SSL certificates have a key pair: a public and a private key. These keys work together to establish an encrypted connection. The certificate also contains what is called the “subject,” which is the identity of the certificate/website owner. To get a certificate, you must create a Certificate Signing Request (CSR) on your server. This process creates a private key and public key on your server. The CSR data file that you send to the SSL Certificate issuer (called a Certificate Authority or CA) contains the public key. The CA uses the CSR data file to create a data structure to match your private key without compromising the key itself. The CA never sees the private key. |
New certificate and key can be uploaded to the system the following way:
|
If the HTTPS certificate request/upload tool is enabled on your LearningSpace system, the page will look as below:
For a step-by-step guide to the go to How to use the HTTPS certificate request/upload tool. |
Country Name (full name) [e.g.: United States of America]
State or Province Name (full name) [e.g.: Some-State]
Locality Name (e.g. city) [Charleston]
Organization Name (e.g. company) [e.g.: Internet Widgits Pty Ltd]
Organizational Unit Name (e.g. section) [College of Nursing]
Common Name (e.g. server FQDN) [e.g.: somecollege.edu]
Email Address [university@edu.cc]
NOTE: If the relevant authority does not provide possibility for generating a CSR, either the local IT department or the LearningSpace Support Team can do it - if given the above data. |
IMPORTANT: When generating a CSR, a CSR file and a key is created. The key has to be treated with the utmost discretion: it must not be shared even with the certificate signing authority. |
If the signing authority is not a root CA, then a so-called Intermediate or Chain certificate is also provided along with the SSL certificate. In such case, the Intermediate/ Chain certificate has to be copied into the signed certificate in the following way:
IMPORTANT: In many cases, the signed certificate does not contain a last line-break. If the content of the intermediate certificate is pasted without the last line-break, it can result in error in file format. When uploading such an erroneously formatted file (see example below), it renders the operation of the web-server impossible and the LearningSpace system inaccessible! |
-----BEGIN CERTIFICATE----- ............ (full content of the signed certificate) ...... HVbLN9xKezHPBf28I2IEy+9RK1ftSyKezXzE51GXgJxH4TFbDt94QIfVJsiKAhPX ............ (full content of the intermediate certificate) ...... Ot80gu+xtYI+H9MF66JrTSjzXlPS8BVkpH61QU1k5nZ7cmz2EGpDUygZvF4S5f0E |
HVbLN9xKezHPBf28I2IEy+9RK1ftSyKezXzE51GXgJxH4TFbDt94QIfVJsiKAhPX -----END CERTIFICATE----------BEGIN CERTIFICATE----- SW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMRMwEQYDVQQDDApleGFtcGxlLmNhMIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvNhKYOOMWBVmVpZVc49WBfG6 |
Learn more on our System Manager pages. |