How to configure your mobility server to use a self-signed cert for testing purposes

From MicroFocusInternationalWiki
Jump to: navigation, search
Return to Data Synchronizer Device Page

Data Synchronizer Mobility Connector

In order to be able to use Mobility Pack with a self-signed cert (normally for testing purposes), you'll need to follow these instructions: NOTE: You can name the .key and .cert files anything you'd like initially because you're going to need to change it to "mobility.pem" later.

  1. Open the terminal
  2. Perform the following commands:
    1. openssl genrsa 1024 > anything.key
    2. chmod 400 anything.key
    3. openssl req -new -x509 -nodes -sha1 -days 365 -key anything.key > anything.cert
  3. Now that you've created the key and cert file you need to concatenate the two files into a .pem file with this command, private key first, then cert. You can also remove the .key file for security purposes in the same command.
    1. cat anything.key anything.cert > anything.pem \ && rm anything.key
    2. chmod 400 anything.pem
  4. Once you've created the .pem file you need to rename it to "mobility.pem" and then replace it with the mobility.pem file in /var/lib/datasync/device.
  5. WinMobile devices require a .cer certificate file (as opposted to .pem). You'll need to create a copy of the .pem file and convert it to .cer:
    1. openssl x509 -in mobility.pem -inform PEM -out mobility.der -outform DER
    2. rename the mobility.der to mobility.cer and move it in the /var/lib/datasync/device directory.
  6. Restart the connectors and resync with your device
  7. Now you shouldn't have cert issues with your device while trying to connect with your self-signed cert.