Skip to main content
Solved

Error occurred after delivery deployment "F1mage failed to sign client".

  • August 24, 2021
  • 3 replies
  • 916 views
S
Sidekick (Employee)
Forum|alt.badge.img+5

Hello,

 

While installing a fix in App10 which possess DB and Client changes, encountered the following error in the configuration.log.

Error in Ant-script: client\build_client.xml

Reported error is: The following error occurred while executing this line:

C:\XXXXX\repository\client\build_client.xml:252: The following error occurred while executing this line:

C:\XXXXX\repository\client\build_client.xml:314: The following error occurred while executing this line:

C:\XXXXX\repository\client\build_client.xml:340: The following error occurred while executing this line:

C:\ifs_BROO5_BNT5APP10\repository\client\build_client.xml:506: F1mage failed to sign client

 

This was the first time we encountered such an error in the environment. I think in the previous installations the F1mage has been correctly signed. Please help to resolve the error.

 

Cheers,

Sasika

Best answer by Bhagya Wickramasinghe

Hi Sasika,

Can you please check the option provided in the “Client Signing”?

 

 

If option “Use same certificate as web server” is selected, then it will use the same certificate as the web server for client signing.

If option "Use self-signed test certificate" is selected, then it signs with a self-signed certificate. This option should only be used for testing purposes.

If option "Import third-party certificate" is selected, then it signs using an imported certificate.

Ideally option 1 or 3 should be used and option 2 is only for testing purposes. Please check this parameter. You can re-configure the instance providing the correct option at “Client Signing”

 

Best Regards,

Bhagya

    This topic has been closed for replies.

    3 replies

    R
    Hero (Partner)
    Forum|alt.badge.img+13
    • Ruchira
    • Hero (Partner)
    • August 24, 2021

    Hi @Sasika Senaratna 

    Try my investigation plan explained below;

     

    Cheers | Ruchira
      B
      Superhero (Employee)
      Forum|alt.badge.img+13

      Hi Sasika,

      Can you please check the option provided in the “Client Signing”?

       

       

      If option “Use same certificate as web server” is selected, then it will use the same certificate as the web server for client signing.

      If option "Use self-signed test certificate" is selected, then it signs with a self-signed certificate. This option should only be used for testing purposes.

      If option "Import third-party certificate" is selected, then it signs using an imported certificate.

      Ideally option 1 or 3 should be used and option 2 is only for testing purposes. Please check this parameter. You can re-configure the instance providing the correct option at “Client Signing”

       

      Best Regards,

      Bhagya

        S
        Sidekick (Employee)
        Forum|alt.badge.img+5
        • Sasika Senaratna
        • Author
        • Sidekick (Employee)
        • August 24, 2021

        If option "Use self-signed test certificate" is selected, then it signs with a self-signed certificate. This option should only be used for testing purposes.

        If option "Import third-party certificate" is selected, then it signs using an imported certificate.

        Ideally option 1 or 3 should be used and option 2 is only for testing purposes. Please check this parameter. You can re-configure the instance providing the correct option at “Client Signing”

        Hi Bhagya,

        This was the issue, self signed test certificate was used.

        After setting it to same as web server and reconfiguring, the issue was solved.

        Thanks and Best Regards,
        Sasika

          Terms & ConditionsCookie settingsAccessibility statement