Skip to Main Content

E-Business Suite

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

AutoVue DMS integration failing on WebSphere

2923772Apr 2 2015 — edited Apr 24 2015

Hi All,

We have an AutoVue DMS integration which is working fine when hosted in Tomcat, JBoss and WebLogic, but is failing in WebSphere 8.5.  The error shown to the user in the applet is "Failed to connect as an unauthenticated user".

If we put debug logging on in the AutoVue server, we see that it sends the request for "PK" and it gets a response, immediately followed by a warning saying "Could not query DMS user name", with this stack trace:

com.cimmetry.core.DMSRemoteException: Error executing DMS request

   nested exception is:

    java.io.IOException: Failed to encrypt DMS Authorization tag contents.  Encrypter: Invalid KeySpec

   nested exception is:

    java.security.spec.InvalidKeySpecException: Inappropriate key specification

This is then followed by this error:

    ServerProxy: Exception in exec(sessionOpen)

    com.cimmetry.core.VueRemoteException: ERROR_UNAUTHENTICATED

     at com.cimmetry.jvueserver.VCETConnection.sessionOpen(Unknown Source)

(The above is then repeated a few times.)

The main difference I can see is that when the response comes back from Tomcat (which works), it looks as follows:

<?xml version="1.0" encoding="UTF-8" ?>

<CSIDATA>

    <Response>

        <ERROR>

            <SUCCEED code="0" message="Returning properties"></SUCCEED>

        </ERROR>

        <GetProperties>

            <Property name="PK"><![CDATA[MIIBpjCCARsGCSqGSIb3DQEDATCCAQwCgYEArt4oa9EgAWsGMjmnM2FdvRqgCnL3TsFbbmIyA8Kh

+GWbCOHbCpXltqwwLSKe4sT0DFdxG9J6STy7Lzb2vnyqmPCxOB35jcFNZ5lK33yO84+AM5UWbs8f

vTWq8jqbG5GbPoSyNJVjnHVr9szU8IdcGhQ6U3TxVtQ8s5rdPR2QQbUCgYEAqU3RwyeJHfap9vf4

...

But from WebSphere (which doesn't work) it's coming back like this:

?xml version="1.0" encoding="UTF-8" ?>

<CSIDATA>

    <Response>

        <ERROR>

            <SUCCEED code="0" message="Returning properties"></SUCCEED>

        </ERROR>

        <GetProperties>

            <Property name="PK"><![CDATA[MIIBpjCCARoGCSqGSIb3DQEDATCCAQsCgYEA5spGmNYgwsE1yeb0Grv3qiOzyUbmykaY1iDCwDXJ]]><![CDATA[

5vQau/eqI7PJRubKRpjWIMK/Ncnm9Bq796ojs8lG5spGmNYgwr41yeb0Grv3qiOzyUbmykaY1iDC]]><![CDATA[

vTXJ5vQau/eqI7PJRubKRpjWIMK7ykQJ2pdF+rCqPvlofdYIak0kDOUCgYA09aItj/XTpMq9bKF4]]><![CDATA[

2neQQ1cqI75Vuitye8KVcHRfMVElwaktPb+vRiHEjTSSzSgQvQMACKLgIKEHZxZVZZalKETEWFzy]]><![CDATA[

Notice the CDATA tags at the end of each line.

So one possibility I guess is that the way WebSphere is handling the carriage returns isn't compatible with the way AutoVue is expecting them.  Another option is this is a red herring and it's just that WebSphere is returning an invalid PK value for some reason.

In case it's relevant, if we set "jvueserver.authentication.enable=false" we end up with a null pointer showing in the applet, but looking at the logs we're actually getting the same problem as shown above.  It basically looks like AutoVue can't do the security handshake with our DMS integration servlet when it's running in WebSphere.

We are using AutoVue 20.2.3 with WebSphere 8.5.  We've upgraded to WebSphere 8.5.5, and tried it both with Java 1.6 and Java 1.7 (using IBM's JDKs).  None of these changes have made any difference.

Anyone got any ideas?

Thanks in advance,

Yoni.

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 22 2015
Added on Apr 2 2015
11 comments
2,415 views