|
|
Common Practices Fireware Pro Firebox SSL VPN Firebox X Core/Edge Setup - Branch Office VPN (IPSec) - Firebox/Soho Remote User configuration using MUVPN & PPTP Troubleshooting - Backing Up/Restoring your Firebox Image.
|
How to use the Microsoft CA Server to create and install a certificate on your SSL VPN 5.0
Created: Nov 12, 2006 Contributed by Jerry Hwang This document is valid for the WatchGuard SSL VPN 5.0 Summary This document provides information on how to us Microsoft Certificate server for use with WatchGuard SSL VPN Gateway. These steps were taken on a Windows 2003 Server with the Microsoft Certificate Authority component installed.
Network
Setup:
MS
Certificate Server / Resource server
SSL VPN Admin
Tool / SSL VPN Client
Procedure
2. Select
‘Stand-alone root CA’
3. I will use
ssl.seattle.com for SSL VPN Gateway FQDN.
4. You may
keep this setting.
5. Generate .csr on SSL VPN Gateway
6. Save the myserver.csr locally
7. Go to MS Certificate site to
request for Server certificate for SSL VPN Gateway.
Select ‘Request a certificate’
8. Select ‘Advanced certificate request’
9. Select ‘Submit a certificate request by
using a base-64-encoded…’ 10. Open ‘myserver.csr’ file and copy the whole contents.
11. Paste it like below. 12. Request is done.
Now go to MS CA Mgmt UI to issue the pending request.
14. Now, you need to download the issued
certificate.
15. Click the issued certificate.
16. Download certificate.
17. Save it locally as certnew.cer
Now you go to SSL VPN Gateway again with the certnew.cer file.
18. Open the certnew.cer file and copy the whole contents.
19. Paste in a new text file and name it as seattle.crt. 20. Upload it to SSL VPN Gateway.
21. Browse the ‘seattle.crt’ file and upload it. 22. You will see the certificate upgrade successful.
And now each SSL Client needs to have the MS certificate server as its root CA that is mostly done in the customer site.
Go to http://192.168.1.2/certsrv to trust certificates issued from the 192.168.1.2 Certificate Authority.
22. Click ‘Install this CA certificate chain’.
23. Customers are supposed to know how to install this CA certificate chain to their users’ web browser.
And the below are the general SSL VPN setting for Secure Access Client mode and Kiosk mode. 24. Local authentication and authorization setting.
25. ‘Group1’ setting for user ‘rickylee’
26. Kiosk setting
Secure Access Client access Now if the SSL user try to access https://ssl.seattle.com, he will see the certificate is issued by trusted CA and certificate date is valid and name on the certificate matches the name of the site. So everything is valid and also you won’t see the security warning by ‘Secure Access Client’ agent. Kiosk mode access (JRE 1.5.09)
Kiosk mode access (JRE 1.4.2.12)
|
|
|