We’re excited to announce that the latest information is now available on our new site, the
Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!">
We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!

">

We’re excited to announce that the latest information is now available on our new site, the
Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!">
We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

Ginesys has capability to capture of item image directly through a connected camera. Web browser should be grant access to connected camera to stream the images into Ginesys. As a pre-requistes, Ginesys web must be accessed over a secured HTTPS protocol, else modern browsers don't allow to enable camera integration. HTTPS can be configured, either using a valid SSL certificate purchased from digital certificate vendor or using a self-signed certificate (self prepared). Obviously the self-signed certificate has certain limitation and ideal for dev-test environment. For production environment, it is always recommended to use a valid SSL certificate.

Limitation of self-signed certificates

It is strongly recommended to use a valid purchased SSL certificate issued by Certificate Authority in production web server.

Following are the limitation of self-signed certificates

  • All digital certificate comes with an validity of 3 years or more. But the self-signed certification is valid for a year only. So you need to keep renewing it every year.
  • The encryption may not be efficient enough to prevent cyber attack.
  • When using a self-signed certificate, the browser will detect the site as suspicious (phissing site) and warn before displaying the site. You have to override the warning manually every time you browse. This will create a mal-practice among users and may be wrongly applied for actual phishing sites.

The following steps would guide users to generate a self-signed certificate and implement in IIS to access Ginesys application over HTTPS URL.


  1. Open IIS Manager (version 7 or above) by running inetmgr from Run command or browsing from Administrative Tools folder in Start Menu.

     

  2. Select the Server on the left hand pane and select Server Certificates in the middle pane.

     

  3. Right click Server Certificates and select Open Feature.

     

  4. Once the Server Certificate feature opens in the middle pane, select Create Self-Signed Certificate.

     

  5.  In Create Self-Signed Certificate window provide a name for the certificate you wish to create. Select Personal in the Select a certificate store for the new certificate.

     

  6. The certificate with the given name will be registered automatically in the particular machine.

     

  7. Now select Default Web Site in the left pane.



  8. Select SSL Settings and right click to select Bindings

     

  9. In Site Bindings window, click on Add.

  10. In Add Site Binding, select https as Type and provide Port - 443. The default Port for https is 443.

     


  11. In the SSL Certificate drop-down, select the name of the certificate created by you in Step Number 6.
     


  12. Then click OK.

  13. Now close the Site Bindings window.

  14. Now open the Ginesys application in your browser with https notation before your application name ( https://<machine name>/GINESYSWeb/UI/index.html).

  15. You may see this anti-phishing error message kick in:

    Don't panic if this happens - it is just your browser being helpful by suggesting that a self-signed certificate on your local machine looks suspicious. Click the "Continue to this website" link to bypass this security warning and proceed to the site. 


  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.