How to resolve Signing key is not found for the assertion keystore with sys_id: ********************

Pooja Kulkarni
Tera Contributor

‎03-21-2023 02:06 AM

We have configured SuccessFactors spoke v4.0.1 as per the document : https://docs.servicenow.com/bundle/tokyo-application-development/page/administer/integrationhub-stor...

 

After the execution of flow action "Retrieve worker profile", we are getting the error "Signing key is not found for the assertion keystore with sys_id:*********************".

 

Please suggest!

0 Helpfuls
  • 1,312 Views
3 REPLIES 3

Mohith Devatte
Tera Sage
Tera Sage

‎05-31-2023 06:33 AM

@Pooja Kulkarni Were you able to fix this issue by any chance?

0 Helpfuls

SUSHMA PINNINTI
Tera Contributor
In response to Mohith Devatte

‎06-26-2023 09:38 AM

Make sure Signing alias key is same as Alias key while generating the certificate in Successfactor...if u don't have it noted but have the certificate in your system then run this command in command prompt 

Keytool-list-v-keystore{their keystore name}.

If this solves your issue please mark it helpful and complete it

hamed_abdy
Tera Contributor
In response to SUSHMA PINNINTI

‎11-05-2024 06:31 AM

Thumbs up for the command line.
Thanks, solved our issue.

In other words, the "keystore name" corresponds to the .jks keystore added into x509 certifs table. 

Get that and use the command above to get the Alias name from keystore.

 

0 Helpfuls