Commodore
Commodore
470 views

SOAP Service Now calling

Hi there,

We are using IDM v4.7 on a windows system . Now we are trying to call a soap service of servicenow by workflow but we are getting the following error.

Workflow Error: Process requestId [1b28c3e35e3f44ceaed47cd77d1c4c9c], Id [cn=servicenow2,cn=RequestDefs,cn=AppConfig,cn=User Application Driver,cn=driverset1,o=system], Integration activity [Activity]: faulted [<?xml version="1.0" encoding="UTF-8"?><m:FaultInfo xmlns:m="http://novell/extendComposer/SystemFault"> <m:DateTime>Mon Dec 17 13:23:14 IST 2018</m:DateTime> <m:ComponentName>Identity Vault_User Application Driver_servicenow2_Activity</m:ComponentName> <m:MainCode>-1</m:MainCode> <m:SubCode>1</m:SubCode> <m:Message>com.sssw.b2b.rt.GNVException: rt007005:Error encountered executing WSDL Action:; ---> nested java.lang.RuntimeException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target</m:Message> </m:FaultInfo> ].

But when we are calling from the tool SOAP ui. It's working perfectly.


Please advice me how to integerate Service now SOAP through workflow.

Thanks!
Labels (1)
0 Likes
2 Replies
Admiral
Admiral

On 17.12.18 11:54, frankabhinav wrote:
>
> Hi there,
>
> We are using IDM v4.7 on a windows system . Now we are trying to call a
> soap service of *servicenow* by workflow but we are getting the
> following error.
>
> Workflow Error: Process requestId [1b28c3e35e3f44ceaed47cd77d1c4c9c], Id
> [cn=servicenow2,cn=RequestDefs,cn=AppConfig,cn=User Application
> Driver,cn=driverset1,o=system], Integration activity [Activity]: faulted
> [<?xml version="1.0" encoding="UTF-8"?><m:FaultInfo
> xmlns:m="http://novell/extendComposer/SystemFault"> <m:DateTime>Mon Dec
> 17 13:23:14 IST 2018</m:DateTime> <m:ComponentName>Identity Vault_User
> Application Driver_servicenow2_Activity</m:ComponentName>
> <m:MainCode>-1</m:MainCode> <m:SubCode>1</m:SubCode>
> <m:Message>com.sssw.b2b.rt.GNVException: rt007005:Error encountered
> executing WSDL Action:; ---> nested java.lang.RuntimeException:
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to
> find valid certification path to requested target</m:Message>
> </m:FaultInfo> ].
>
> But when we are calling from the tool SOAP ui. It's working perfectly.
>
>
> Please advice me how to integerate Service now SOAP through workflow.
>
> Thanks!
>
>


This is an SSL error:


javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target</m:Message>
</m:FaultInfo> ].

As far as I remember SOAP UI will automatically import any unknown
certificates into it's keystore which is why you're getting this error.

Suggestion would be to import the public certificate from servicenow
into the Tomcat's Java Keystore.


Casper
0 Likes
Micro Focus Expert
Micro Focus Expert

On 12/17/18 6:50 AM, Casper Pedersen wrote:
> On 17.12.18 11:54, frankabhinav wrote:
>>
>> Hi there,
>>
>> We are using IDM v4.7 on a windows system . Now we  are trying to call a
>> soap service of *servicenow* by workflow but we are getting the
>> following error.
>>
>> Workflow Error: Process requestId [1b28c3e35e3f44ceaed47cd77d1c4c9c], Id
>> [cn=servicenow2,cn=RequestDefs,cn=AppConfig,cn=User Application
>> Driver,cn=driverset1,o=system], Integration activity [Activity]: faulted
>> [<?xml version="1.0" encoding="UTF-8"?><m:FaultInfo
>> xmlns:m="http://novell/extendComposer/SystemFault"> <m:DateTime>Mon Dec
>> 17 13:23:14 IST 2018</m:DateTime> <m:ComponentName>Identity Vault_User
>> Application Driver_servicenow2_Activity</m:ComponentName>
>> <m:MainCode>-1</m:MainCode> <m:SubCode>1</m:SubCode>
>> <m:Message>com.sssw.b2b.rt.GNVException: rt007005:Error encountered
>> executing WSDL Action:; ---> nested java.lang.RuntimeException:
>> javax.net.ssl.SSLHandshakeException:
>> sun.security.validator.ValidatorException: PKIX path building failed:
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to
>> find valid certification path to requested target</m:Message>
>> </m:FaultInfo> ].
>>
>> But when we are calling from the tool SOAP ui. It's working perfectly.
>>
>>
>> Please advice me how to integerate Service now SOAP through workflow.
>>
>> Thanks!
>>
>>

>
> This is an SSL error:
>
>
> javax.net.ssl.SSLHandshakeException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to
> find valid certification path to requested target</m:Message>
> </m:FaultInfo> ].
>
> As far as  I remember SOAP UI will automatically import any unknown
> certificates into it's keystore which is why you're getting this error.
>
> Suggestion would be to import the public certificate from servicenow
> into the Tomcat's Java Keystore.
>
>
> Casper


Greetings,
In addition to what Casper outlined, you will need to restart the
Tomcat Application server after you update the Java Keystore file
(normally the cacerts file). If you are deployed in a cluster, you will
need to perform this on all nodes. Also, make sure you import the
entire trust chain [root, intermediate (if there is one), and singed]
or else it will not work.

--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.