PAM 04.3.03 - SOAP call creating a ticket which has PAM workflow fails - java.security.NoSuchAlgorithmException

[J W]

(Note.  Not related to earlier PAM discussion concerning empty Library folder)

PAM 4.3.03 integrated with SDM 17.1.02.  This is the test/QA environment.  This is an SSL setup.

We have a dedicated web services app server in this AA environment.

Creating SDM tickets via SOAP works unless there is a PAM workflow attached to the ticket category.  Then, it only works when pointing to the Background server and not the Web Services App server.

The error returned in soapUI is:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Client</faultcode>
         <faultstring>INVALID ; nested exception is: 
	java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext); nested exception is: 
	java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)</faultstring>
         <faultactor/>
         <detail>
            <ErrorMessage>INVALID ; nested exception is: 
	java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext); nested exception is: 
	java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)</ErrorMessage>
            <ErrorCode>1</ErrorCode>
         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>​

Looking online for this error code points to possible keystore issues and/or versions of Tomcat.  Both SDM servers are running Tomcat 8.5.6.0.  The JVM version on both servers is:  1.8.0_112-b15.

I'm not sure where to check for differences between the servers that might relate to this.

Any guidance will be appreciated.

J.W.






------------------------------
"No matter where you go, there you are." - TAoBB:AtED
------------------------------

[Michael Mueller]

Hi.
I assume, there is a missing/wrong ssl setup on your webservice app server.
Does tue ticket creation works from your gui app Servers?
What do you mean by ssl setup?
Ssl for pam and SDM gui and soap?
As a starting point compare nx.env from bg and soap app server regarding pam integration. 
Check jstd.log on soap app server for additional hints.
INVALID is a keyword which comes from the checkin/save activity.
The rest of the message is coming from the rpc daemon, I assume.
This java daemon communicates to pam....
For https, the keystore needs to be setup correctly.
Check, what you did on the bg to setup ssl to pam.
Maybe you have to do the same in your soap app server as well.
Regards 
.....Michael




------------------------------
Principal Services Consultant
HCL Enterprise Studio
Germany
------------------------------

[J W]

Thanks, Michael.

We are looking into these.  There was no additional information in the jstd.logs other than the same error message.  I saw a difference is the EEM CERT PASSWORD fields between the Background and Web Services App servers NX.env files.  I am having the engineers review the integrations and certs.

J.W.

------------------------------
"No matter where you go, there you are." - TAoBB:AtED
------------------------------

[Pier Olivier Tremblay]

It looks a lot like the error I was getting before importing PAM cert into SDM keystore.

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=9538

Have fun

[J W]

Ended up redoing the entire cert process again.  There were no errors to trace where the procedures differed from the first setup.

Thanks,

J.W.

------------------------------
"No matter where you go, there you are." - TAoBB:AtED
------------------------------