Bulk Materials Ideas
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
Idea and discussion portal for the bulk materials product line. Users may submit, view and vote on ideas submitted by all users.
Right now the Web Wireless Loader only works with HTTP. To stay current with security protocols, we want the services to work on HTTPS.
Background/Current State
We have wireless loader at 3 sites and want to expand to even more of our sites. Our locations do not have wifi that would reach to the locations on the property where the Loaders are located. So we use cellular connections. We use Citrix to authenticate from the Android tablet to our server running Wireless Loader. This is clunky and requires too many steps to get into the Loader screen. For the 10 loaders we have in place, IT receives a support call 1 to 2 times a day. And this is after the Plant Operator has spent time troubleshooting.
Future State
We want to use Azure's Proxy service which allows us to publish internal web pages externally by using Microsoft's SSO, but this requires the webpage and the services running behind it to be HTTPS. We would be able to lock the Android tablet down to launch this webpage directly in the tablet's browser, therefore keeping the cached settings on that tablet. Then they will only need to log in every 14 days instead of every day.
Other Notes
Even if we went with the suggested VPN to cellular device, our security team still will require it to run as HTTPS. This is restraining us from buying and installing Wireless Loader across our organization.
I understand now. I checked with one of our developers, it does seem that this would be a code change after all.
Hey Chris, We are able to get the Web page to work fine with out SSL certs. But all current browsers to not allow a mismatch between the Webpage and the services behind it. The web is HTTPS while the services only support HTTP. These are the Ticket.VehicleInPlant.exe and the Ticket.VehicleInPlantService.exe.
Logan,
As this application is not hosted on CA servers, we cannot control SSL certifications easily. As such, our default install is HTTP only. This doesn't mean HTTPS doesn't work. You will need to obtain an SSL certificate, and bind the website in IIS to HTTPS with that certificate. Feel free to reach out to me for additional details if needed.
Here's a link that might also help shed some light on what I'm talking about:
https://www.digicert.com/csr-creation-ssl-installation-iis-10.htm