When a wildcard certificate is included in a keystore, JBoss will present the wildcard certificate to the client requesting it. The client will then need to verify the certificate with a trusted CA Root Authority. If the certificate is not present, most browsers with the "Certificate Request" feature, will keep requesting the intermediate certificates until the identity is verified with the trusted Authority. This can be a problem for basic browsers, or browsers that do not support "Certificate Request" as the certificate is never verified and appears invalid. This issue is even more specifically found on Android devices and can be found using an SSL Verifier.

Prerequisites

• Download and install OpenSSL on the server.
• Download the issued wildcard certificate (PFX), the password file, as well as the following certificates from the GoDaddy Repository
  • valicert_class2_root.crt
  • gd_cross_intermediate.crt
  • gd_intermediate.crt

You will want to copy the .PFX and the .CRT files to a folder, and then copy this folder to the OpenSSL \bin folder to execute the following commands. The complete path should resemble "C:\OpenSSL-Win32\bin\Certs".

Solution

You now need to open a command prompt and navigate to the OpenSSL\bin to use these commands:

Export and decrypt the .PFX

• openssl pkcs12 -in ".\Certs\wildcardcert1.pfx" -out ".\Certs\wildcard2.pem" -nodes

Copy the password from the password file to complete.

Now export and decrypt the certificate from the .PFX

• openssl pkcs12 -in ".\Certs\wildcardcert1.pfx" -out ".\Certs\wildcert3.pem" -nodes -clcerts

Again, copy the password from the password file to complete.

Now we need to verify the conversion of the exported certificate.

• openssl x509 -in ".\Certs\wildcert3.pem" -out ".\Certs\newwildcert4.cer" -outform DER

We now need to open wildcard2.pem in Notepad and append the certificate chain in the correct order.

Open gd_intermediate.crt in Notepad and copy the entire content of the file including the "----- BEGIN CERTIFICATE -----" and "----- END CERTIFICATE -----" tags and paste the text at the end of the wildcard2.pem file.

Repeat the previous step with gd_cross_intermediate.crt, appending it to the last copied certificate.

Once again, we repeat the previous step with valicert_class2_root.crt appending it again to the last copied certificate.

We can now save the new completed certificate. The next step is to reconvert it to .PFX and encrypt it again. We can achieve this with the following command (the name can be anything short, using only ASCII characters):

• openssl pkcs12 -export -in ".\Certs\wildcard2.pem" -out ".\Certs\newwildcardcert.pfx" -name "root"

You now need to generate a new password, and the file is complete.

You can now copy the newwildcardcert.pfx file to the server \conf folder "C:\Adobe\Adobe LiveCycle ES3\jboss\server\lc_turnkey\conf".

Now we need to navigate to the server.xml found at "C:\Adobe\Adobe LiveCycle ES3\jboss\server\lc_turnkey\deploy\jbossweb.sar" and open the server.xml file in Notepad. We can then modify the SSL connector with the following:

<!-- SSL/TLS Connector configuration using the admin devl guide keystore -->

      <Connector protocol="HTTP/1.1" SSLEnabled="true"

               port="443" address="${jboss.bind.address}" URIEncoding="UTF-8"

               scheme="https" secure="true" clientAuth="false"

               sslProtocol = "TLS"

               keystoreFile="${jboss.server.home.dir}/conf/newwildcardcert.pfx"

               keystorePass="password"

               keystoreType="PKCS12"  />

Save the file and give the JBoss server a restart. Keep an eye on the log, and verify that everything deploys correctly.

Conclusion

After everything is done, we can verify all of our hard work with this handy SSL Verifier.

Sources:

• Certificate conversion: http://stackoverflow.com/questions/6654543/how-to-create-pfx-with-my-chain-of-certificates
• Certificate chain creation : http://support.godaddy.com/help/article/5239/generating-a-csr-and-installing-an-ssl-certificate-in-tomcat-4x5x6x
• Installing PFX on JBoss : https://www.globalsign.com/support/install/install_pfx_jboss.php

http://blogs.adobe.com/ADEP/2012/01/the-future-of-livecycle.html

Depending on your renderer version you might run into an issue where a page header is being bumped back to the bottom of the previous page. This is a known issue with version 2.6 of the XFA specification which was fixed in version 2.7. The tricky part is there's no Target Version for version 2.7. If you aren't familiar with Target Version, click on File then open Form Properties and check the Defaults tab.

The easiest solution is simply setting your Target Version to Acro/Reader 9.0 (which uses XFA version 2.8), but this will cause problems for people still running Reader 8.

We did some digging and found an easy way to trick the form into using XFA 2.7 to render the form. Open the XML view of the document and find the following line:

<?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.6/?>

And change it to this:

<?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.6/ v2.7-layout:0?>

After that you'll want to make sure Keep With is set to Next in the headers pagination settings.

If you're currently having difficulties running Office after installing the Rights Management plugin there's a very good chance you also have the Microsoft Office Live plugin installed as well.

These two plugins simply do not work together and you'll need to remove one of them until either Microsoft or Adobe fix the conflict.

We recently encountered an issue when merging XML data into a form.  Specifically, rich text was being properly displayed in the form fields, but we noticed that any floating fields placed in those text fields displayed their value in plain text.

This can be resolved by manually changing the embedMode tag in the forms XML. Click on the object containing the floating field then open the XML Source view. Inside the object you'll be looking for this:

We recently encountered an issue when merging XML data into a form.  Specifically, rich text was being properly displayed in the form fields, but we noticed that any floating fields placed in those text fields displayed their value in plain text.

This can be resolved by manually changing the embedMode tag in the forms XML. Click on the object containing the floating field then open the XML Source view. Inside the object you'll be looking for this:

xfa:embedMode="raw"

You'll want to change it to:

xfa:embedMode="formatted"

As always, if you run into any problems be sure to give us a call!