Problem attaching Policy on PDF using PDFManipulation.exe in Security Server. [GIOP 1.2 protocol err

[Former Community Member]

Hi,



I'm using Policy Server 7.0.1 and Security Server on Windows 2003 and JBoss 3.2.5. I have Adobe Policy Server and Adobe Security Server both deployed on the same JBoss instance. Security is configured using SSL.



I'm trying to attach a Policy to a PDF using the PDFManipulation tool inside the Security Server API.



I have a Servlet successfully connecting to Policy Server, I'm looking up the PDFManipulation in the JNDI, creating a transaction and are trying by the ConnectionFactory class to get a connection to the native PDFManipulation.exe. I'm getting the error message : "Detected GIOP 1.2 protocol error in input message".



So I wonder is the IOR String [IOR:00000000000000224...] wrong or what?

Anyone out there recognize this error?



regards

Jerry Johansson

Perth, Australia



-----------------------------------------------------



This is my code:



private PDFDocument getPDFDocument(String rawPDFPath)

{

try

{

InitialContext ctx = new InitialContext();

Object pdfObject = ctx.lookup("PDFManipulation");

ConnectionFactory pdfConnectionFactory = (ConnectionFactory)

PortableRemoteObject.narrow(pdfObject, ConnectionFactory.class);

UserTransaction trans = (UserTransaction)ctx.lookup("java:comp/UserTransaction");

log.debug("UserTransaction " + trans);



trans.begin();



PDFFactory pdfFactory = PDFFactoryHelper.narrow((org.omg.CORBA.Object) pdfConnectionFactory.getConnection());



// !!!! EXCEPTION happens above.



-----------------------------------------------------



This is the log:



2005-06-23 16:02:29,562 DEBUG [com.ebooks.ebl.onlinereader.aps.factory.OnlineReaderPolicyFactory] UserTransaction org.jboss.tm.usertx.client.ServerVMClientUserTransaction@40f2f1



2005-06-23 16:02:29,718 INFO [com.adobe.service.logging.Logger] $$$/server/service/logging/msg.LogSvcInit=Logger com.adobe.service.logging.Logger initialized



2005-06-23 16:02:29,781 INFO [com.adobe.document.PDFManipulation] Service PDFManipulation: Creating the temporary directory for managed process.



2005-06-23 16:02:30,843 INFO [com.adobe.document.PDFManipulation] Service PDFManipulation: Starting native process with command line C:\APS\Adobe\LiveCycle\PolicyServer\jboss-3.2.5\server\all\svcnative\PDFManipulation\bin\PDFManipulation.exe -IOR IOR:000000000000002249444C3A636F6D2F61646F62652F736572766963652F4D616E616765723A312E30000000000000020000000000000088000102000000000E3139322E3136382E302E313434000DC8000000134A426F73732F42522D312F0100000000000000000000000400000014000000080000004000600DC90000000000000008000000004A414300000000010000001C000000000001000100000001050100010001010900000001050100010000001400000008000000E000600DC9000000010000002C0000000000000001000000010000001C00000000000100010000000105010001000101090000000105010001 -KeyPass YmVkcm9jaw== -CertPath "C:\APS\Adobe\LiveCycle\PolicyServer\jboss-3.2.5\server\all\svcnative" -SSLNativeDir "C:\APS\Adobe\LiveCycle\PolicyServer\jboss-3.2.5\server\all\svcnative\ServicesNatives2\lib" -AppServer jboss



2005-06-23 16:02:35,296 INFO [STDOUT] omniORB: From endpoint: giop:tcp:192.168.0.144:3528. Detected GIOP 1.2 protocol error in input message. Connection is closed.



omniORB: From endpoint: giop:tcp:192.168.0.144:3528. Detected GIOP 1.2 protocol error in input message. Connection is closed.



-----------------------------------------------------

[Former Community Member]

After going through the Adobe LiveCycle Policy Server sample (freely downloadable from www.adobe.com, the documents said that the Policy Server disables SDK access by default and there are instructions in the sample on how to enable it.



I believe the reason your code threw an exception was that userTransaction class is meant to be used with the Data Manager. I am not sure why it threw on the PDFFactory call though. I would also check the Document Security Developer's guide as there appeared to be some simple instructions on how to create a document with a policy.

[Former Community Member]

Thanks Dave,

Yes I know that SDK is disabled, you need to export the server configuration XML and enable SDK.



The problem I have is probably related to my generated keys for SSL.

The Corba IOR call was not accepted according to the protocol so I recreated my keys and have all sorts of SSL errors instead now...

When I try to run SignTool.jar I get this, which might be related to my install of Security Server. I think I will just start all over...



Exception in thread "main" java.security.InvalidKeyException: No installed provider supports this key: sun.security.rsa.RSAPrivateCrtKeyImpl at java.security.Signature$Delegate.chooseProvider(Signature.java:1059)

at java.security.Signature$Delegate.engineInitSign(Signature.java:1100)

at java.security.Signature.initSign(Signature.java:485)

at com.adobe.trustmanagerutil.SignOrVerify.Sign(SignOrVerify.java:82)

at SignTool.main(SignTool.java:90)

[Former Community Member]

Hi Jerry -



I realise that you posted these posts over a year ago now, so this is a long shot, but did you solve the issue you had with the 'Detected GIOP 1.2 protocol error in input message' error?



The reason I ask is that I have exactly the same problem - I had an EJB which successfully connected to Document Security Server & applied a policy. I then implemented SSL on the server and now I get this error message every time I try and apply a policy.



If you did get it sorted out could you please let me know how I can get this working?



Many thanks in advance,

Anil.

[Former Community Member]

Hi Anil.



Yes, I remember this problem. I looked in to how the demo application worked. I if I remember right my difference was that I had my connection outside the servlet in another package. When I did as Adobes own demo appl. and made the connection in the Servlet it worked.



I had heaps of other problems later and we decided to wait to develop on APS until Adobe had made the API a bit more stable. This was a year ago, so they've maybe improved the API now...



Good luck.



cheers

Jerry Johansson

Australia

[Former Community Member]

Jerry



I suspect that your problem has someting to do with the configuration of the "jacorb.properties" file used by JBoss (located in Jboss\server\all\conf).



I have configured SSL on JBoss 3.2.5 using credentials that I created to using the Java keytool, I have documented all of the steps that I followed to configure JBoss. I have also been successful in applying a policy (Java Servlet) to a PDF using ALDS with an SSL connection



I can send you the document if you want. You can contact me at steve.forrest@adobe.com. Please not, that this document is not an official Adobe document and it is to be used at your own risk!



Regards

Steve