Let’s say that you decide that you want to enable SSL on your RMS pipelines after RMS is provisioned. It is recommended that you decrypt all RMS-protected content, re-install and re-provision RMS, and then encrypt the content again. However, this is not always possible.
One alternative option is to provision a new RMS environment and redirect all of your RMS clients to use this new license server. Before we see how to do this, there are several assumptions made about your RMS environment:
Whew! Now for the fun stuff. To enable SSL in your RMS environment after the RMS server has been provisioned, you should follow these steps:
The method described in this blog post have not been fully tested and may lead to undesirable effects. For example, rights policy templates and trusted user domains will not be transferred using the steps outlined in this post. The recommended method to enable SSL after RMS is provisioned is to do the following:
Feel free to let you know what you think by posting comments. Your feedback is welcomed.