When you install BCAAA on a machine in your network, it generates a self-signed certificate to use for SSL communication with your ProxySG appliances. This article details the steps to use a certificate signed by a Microsoft PKI or public Certification Authority (CA) server instead.
Here is an overview of the process:
Generate a Certificate Signing Request (CSR) and have it signed by the Microsoft PKI or other CAs.
Import the two web server certificates and the CA certificate to the ProxySG.
Enable SSL communication between the ProxySG and BCAAA.
Install BCAAA and configure it to communicate over SSL only, place the .pfx cert in the BCAAA SSL Store.
You would like to install BCAAA securely, using certificates signed by your own PKI or preferred CA server instead of the self signed certificate.
Part 1: Install BCAAA/Configure Windows Network
Create a DNS A record in your Windows network that points to the Server IP that BCAAA will be installed on, using an Fully Qualified Domain Name (FQDN). The FQDN will serve as a Common Name (CN) for the SSL certificate. An example for the FQDN might be BCAAA.mycompany.com.
Enable SSL on BCAAA during the installation of BCAAA.
Install BCAAA and when prompted, choose Allow only SSL connections.
When prompted if you would like to open or allow the BCAAA port on the server firewall, choose Yes.
Configure the Common Name (CN) as defined in step 1 above, (after making sure that your DNS server is able to resolve the above FQDN).
When prompted to select Save the automatically generated certificate in the certificate store, choose Yes.
When prompted to select Require the ProxySG to provide a valid certificate in order to connect choose No..
Click Install to run the installation process.
Once the BCAAA installation is complete, verify that the bcaaa.ini (located in the BCAAA installation folder) and make sure the configuration appears is as below. If it is different, please modify the bcaaa.ini and restart the BCAAA service.
Generate a Certificate Signing Request (CSR) on the ProxySG. Define the Common Name field as the FQDN you created earlier, that matches the DNS A record pointing to the IP address where BCAAA is installed. For additional detials on this process, see the following KB article: How to generate a CSR on the SG: http://bluecoat.force.com/knowledgebase/articles/Solution/000008819-CreatingaCertificateSigningRequestCSR
Using the CSR generated in step 1 generate a web server certificate on your internal Microsoft PKI or your preferred public CA.
The CA signing process creates two files:
The web server certificate. Give it a name: BCAAA_Cert.cer
The CA Root Certificate. Give it a name: BCAAA_Root_Cert.cer
Export the Certificates from the CA as a Base 64, PEM format. (Consult with you system administrator if you're not familiar with this process).
Import BCAAA_Cert.cer and the BCAAA_Root_Cert.cer to the ProxySG and add them to the trusted certificate store. Steps to do this are as follows:
Open BCAAA_Cert.cer file using a text editor, highlight all text, right-click and select and copy.
On the ProxySG go to Configuration > SSL > Keyrings. Select the CSR BCAAA_Cert generated in step 1 and click Edit, Under the Certificate section, click Import and paste the BCAAA_Cert.cer in PEM format.
In Configuration > SSL > CA Certificate. Under the CA Certificate tab click Import. Name the CA certificate: BCAAA_Web_Cert (for example). Don't give it the same name as BCAAA_Cert as you will get an error, paste the BCAAA_Cert.cer (PEM). Click OK and Apply.
In Configuration > SSL > CA Certificate. Under the CA Certificate tab click Import. Name the CA certificate: BCAAA_Root_Cert (for example). Don't give it the same name as above as you will get an error, paste the CA Root Certificate (PEM). Click OK and Apply.
In Configuration > SSL > CA Certificate, under the CA Certificate List tab, select Browser-trusted and click Edit. Locate BCAAA_Root_Cert and BCAAA_Web_Cert in the list on the left. Use Add>> to move each certificate to the right side. Click OK and Apply.
In Configuration > Authentication > IWA Servers > check Enable SSL. Assign the Primary BCAAA server to use the FQDN as the host address, and not the IP address for that server. Select default under the SSL Device Profile.
Extract the private key of the BCAAA_Cert from the ProxySG, as you will need it to generate a .pfx certificate that is needed for BCAAA Server. Steps and details are as follows:
SSH in to the ProxySG.
Type enable to enter elevated privilege mode.
Type config t to enter configuration termial mode
Type ssl. The prompt displays as (config ssl)
Type view keypair BCAAA_Cert. Note: this is case-sensitive.
Copy everything listed including and between : -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY-----
Paste in to a text file, save the file with a name like BCAAA_Cert_Key. Once the file is saved, change the file extension to .key
Make sure you have the below 3 files before you continue to the next step:
This step is not performed on the ProxySG. You have to convert the three files in to one certificate. This is called a pfx certificate. This certificate is a combination of the Web Cert, Private Key and Root Cert. BCAAA will need this certificate to negotiate the SSL connection with the ProxySG. You can use openssl for this purpose, here is an example of the openssl command that would take the three files and combine them in to one .pfx certificate. You can name the output file BCAAA_certificate.pfx.
openssl pkcs12 -export -out BCAAA_certificate.pfx -inkey BCAAA_Cert_Key.key -in BCAAA_Cert.cer -certfile BCAAA_Root_Cert.cer. If you're not familiar with OpenSSL, consult the openssl forums or other OpenSSL documentation for assistance.
There are other tools and converters you can use to convert a cert, private key and the root in to a .pfx certificate, please contact your system adminstrator for assistance with this step#7
Part 3: Install the PFX certificate on the BCAAA server.
Import the BCAAA_certificate.pfx file in to the BCAAA Certificate Store on the server where BCAAA is installed.
Move the file BCAAA_certificate.pfx to the server desktop where BCAAA is installed.
Stop the BCAAA Service.
Click Start > Run. The Run dialog opens. Follow these steps to install the PFX certificate:
Type MMC in the Run dialog box and then click Ok.
Select File > Add/Remove Snap-in. The Add/Remove Snap-in dialog displays.
Click Add. The Add Standalone Snap-in dialog displays.
Select Certificates from the Snap-in list and click Add. The Certificates snap-in wizard starts.
Select Service Account and then click Next.
Select Local computer and then click Next.
From the Service Account list, select BCAAA, click Finish, and click Close.
Click Ok to save your changes and close the Add/Remove Snap-in dialog.
On the left side you will find Certificates - Service-(BCAAA) on Local Computer.
In the list of certificate elements, select BCAAA/Personal (expand) > Certificates > and then delete any certificates if there are any. (there could be one or two)
Select the Action menu, and select All Tasks >Import. Browse to where the BCAAA_certificate.pfx is located. Place the certificate in the BCAAA/Personal store and click Done.
Windows will import the BCAAA_certificate.pfx and convert it to two files: one file is the will be the web certificate, and the other one file will be the root certificate.
Close the MMC console.
Start the BCAAA service.
To test the configuration, log in to the ProxySG and go to Configuration > Authentication > IWA > IWA Servers. Locate the Test Configuration section and click
Test configuration. The proxy prompts you to enter a valid domain username and password. If successful, the test should succeed.
And if you see errors below, that means that you did not generate the .pfx certificate properly, or it is missing the Private Key.
AcquireCredentialsHandle failed: 0x8009030e; status=-2146893042:0x8009030e:7-010902370 bailout -2146893042(0x8009030e) Failed to establish SSL connection.; status=-2146893042:0x8009030e:No credentials are available in the security package
Take a packet capture between the ProxySG and the server running BCAAA and make sure that proxy has established a succesful TCP hansdake.
Make sure the BCAAA service is running on the server and SSL Is enabled.
Make sure that SSL is enabled on the ProxSG for the BCAAA Realm.
Imported Document ID: 000032876
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.