Skip to main content
Solved

Error loading .P12 certificate in Keystore


E.Mamcasz
Sidekick (Partner)
Forum|alt.badge.img+6

Hello everyone,

We have started implementing E-Sign on Cloud 23R2 and are experiencing problems loading .P12 certificates to be used in the digital signature process for Documents. The message “Error when importing certificate.” returns.

I would like to know if there is any condition that must be met or if there is any interference from Azure in this process.

If anyone knows of any tutorials other than the Cloud Documentation that they can share, I would be grateful.

Sincerely,

 

 

Best answer by E.Mamcasz

Hello everyone,

The error message occurs when the Certificate file is longer than 45 characters. After renaming the file, it can be loaded normally.

We didn't get to test ​@dsj's suggestion.

Best Regards,
 

View original
Did this topic help you find an answer to your question?

5 replies

Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • 2795 replies
  • March 10, 2025

Hi,

The digital signature functionality for PDF files is severely limited on IFS Cloud, are you aware of that? Documents can only be signed using the certificate connected to the user used by IFS Connect. This should be documented in the release notes since IFS Cloud 21R1.

It's also very different from our E-signature functionality (integrating with Adobe Acrobat Sign) that was released in 23R2.

 


dsj
Superhero (Partner)
Forum|alt.badge.img+22
  • Superhero (Partner)
  • 822 replies
  • March 10, 2025

Hi ​@E.Mamcasz 

The error could be due to the certificate content. Is it self signed or generated from a certificate authority?

In order to check if the certificate import functionality working, you can create a new certificate using OpenSSL and try to import.

I use below commands to generate a certificate which could successfully import to keystore

>openssl req -x509 -newkey rsa:4096 -keyout ifs_key.pem -out ifs_cert.crt -sha256 -days 365>openssl pkcs12 -inkey ifs_key.pem -in ifs_cert.crt -export -out ifs_cert_pfx.pfx

If the generated file can import successfully, compare the file content format with your certificate and see if there are any differences.

Even though the certificate import is a success, make sure if the digital signature functionality can be used as you intended according to ​@Mathias Dahl ‘s comment

Hope it helps!

Damith


E.Mamcasz
Sidekick (Partner)
Forum|alt.badge.img+6
  • Author
  • Sidekick (Partner)
  • 15 replies
  • March 10, 2025

Hello Mathias,

Yes, after I opened the topic I found a lot of information and I am aware that they are two different functionalities. The one that meets the Client's requiriments is the first one, but we have this error occurring. I have already identified alternatives here in the Community to show the User who signs in addition to IFSCONNECT, but we are still testing before presenting it to the Customer.


E.Mamcasz
Sidekick (Partner)
Forum|alt.badge.img+6
  • Author
  • Sidekick (Partner)
  • 15 replies
  • March 10, 2025

Hello DSJ,

Thank you for your information. We will evaluate and teste your suggestion with technical support.

 


E.Mamcasz
Sidekick (Partner)
Forum|alt.badge.img+6
  • Author
  • Sidekick (Partner)
  • 15 replies
  • Answer
  • March 12, 2025

Hello everyone,

The error message occurs when the Certificate file is longer than 45 characters. After renaming the file, it can be loaded normally.

We didn't get to test ​@dsj's suggestion.

Best Regards,
 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings