We are in the process of setting up SSL decryption. We have a BYOD wireless network that needs to have SSL decryption turned on. Students can connect with their personal devices, so we need to be able to block Facebook, porn, etc.that are coming in over HTTPS. We've got it working with organization-owned equipment but are having hang-ups with personal devices.
My question is more of a general one to the rest of the users: if you are doing this too, how do you get the cert available to the end user so they can install on their device? We were thinking of having an internal web page that explains the need to install the cert, and have it include a URL to download the cert from the internal web server. I know with other filtering appliances we've had in the past, we did this, and end-users could never figure out how to put the cert in "Trusted Root Certification Authorities" store.
Would there be a better way to handle this?
In the end, we setup an internal web server (IIS7) and have several HTML pages. We also have a link to the SSL-cert and screenshots on how to install it on various client OSs.
We have our Cisco WLC 5508 wireless controller redirecting BYOD guests to this page after they connect.
This was the quickest and simplest way for us.
Yes, that would definitely be the best way to proceed as you cannot have control over machines (pc/laptop/cell/macs) etc to push it through GPO. Once you redirect them, they will need to install the certificate on their devices in order for them to not to get browser's warning. Hope this helps. Thank you.
That's an interesting problem you have stated! Now, if i understand it right
1. You are ok with the users being redirected to a website and installing the Cert
2. What the actual problem is the fact that the users are unable to add the certs without instruction and/or the instructions are difficult to follow
3. We cannot use the GPO technically as they are not a part of the domain and hence we cannot push the certificates
Now, I am making some assumptions
1. All the intended clients are Windows - Multiple versions of them may be
2. All the users may not have administrative access on their computer - A little far fetched but still a remote possibility
We create an installer using C#, which does this for them. Then we can send the installer and not the certificate file. A simple Next, Next Installation will be far easier to follow.
Since we are talking windows, a simple c# program will be sufficient.
1. Convert the Certificate as a x509 format (Open SSL should be able to do this fairly simply)
2. You could create a C# Forms Application with the main install button performing the following
string certFile; // Contains name of certificate file();
X509Store store = new X509Store(StoreName.Root, StoreLocation.CurrentUser);
This will add the Certificate into the Users Root CA (Not the computer account) - Which is sufficient for our purposes
If thats not a possibility, then create a batch bile
2 (Onother Option) . Create a batch file with the content (Name the file installCert.bat or something)
certmgr /add certFile.cer /s Root
And give the certificate in x509 format and the batch file in the same folder. Once people click on the batch file the cert will be installed
Please let me know if you have questions
So, just cl
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!