I have successfully installed a turnkey LiveCycle (WebLogic) server and have written a couple test methods in C# (as proof of concepts). One method I have invokes the rights management web service to apply a policy to a PDF. It appears to work fine, except when the new PDF (with rights) is loaded Adobe Reader tells me:
"You are attempting to connect to an Adobe LiveCycle Policy Server using an insecure protocol (http)....."
And it wont let me view the PDF (which makes sense).
Now I am not sure what else i need to do. I am calling the rights management webservice using the Url: http://testbed:8001/soap/services/RightsManagementService and I get the same "insecure protocol" error as above. If I switch the Url to HTTPS and port 7002, the web call fails with "unable to connect to server". I feel i told weblogic how to use SSL, but LiveCycle needs configuration somewhere to make this work.
I guess I am trying to determine what else I need to do in order to allow me to view my PDFS after I apply rights. This is not production, this is just a testbed so we can write some proof-of-concept code.
Ok i managed to get a little further on my own, but am failing on the SSL. By reading this post from previous LC versions(http://www.adobeforums.com/webx/.3bc0a469/0) I realized i needed to set the BASE URL of the Rights Management service to point to the SSL port, like https://192.168.1.x:8443 and to keep calling the web service using the http://192.168.1.x:8001 url.
Now I can call the service, get back my document with rights, and when I load the document I see it is hitting https://192.168.1.x:8443 (because it tells me), but when I allow this I get the error:
"The computer must be connected to the network in order to open this document."