Hi again, Sorry I havent read the documentation thoroughly. I will investigate below.
Ah, I was over thinking it a bit. Thanks again for all the help. Now I get the same result as you have in your screenshot. Mvh Gustaf
Hi again In order to make the Self-generated certificate Trusted in Adobe I will need the actual pfx-file and import that as a trusted certificate. Correct? But if this was the case Im caught in a moment 22 since I need to export the file from the db in order to import it. And export is not allowed. I obviously have misunderstood something here and if you can guide me a bit how I make the Self-Generated certificate Trusted in adobe I would be greatful. Regards Gustaf
Thanks for your answers, highly appreciated. I will try to make the certificate trusted by Adobe and re-test. And this also answered my Q3. Customer will have some “external” actions like purchasing certificates and also to gain knowledge of how certificates in general works (if the signed documents are to be distributed externally). Mvh Gustaf
Great! Thanks for the response. Q3: Is it possible to list all ‘external’ activities that thecustomer has to take to ensure that this functionality works? Poorly formulated by me. This was in relation to the external ceritficates that I presumed was mandatory. I wanted to hedge if there are several actions that the customer needs to take outside of IFS. Like 1. Ensure external certificates for each person that will sign documents 2. Validate against Adobe to be ‘trusted’ 3. etc ---Based on your answer on Q1 this question is only relevant if the digital signature shall have bearing outside of their own company--- Q2: Providing some screenshots of the issue. This test was done against a standard report using report rule Engine. The signature itself is displayed but with the “error-message” in Adobe. And with this scenario I guess the document is not Digitally Signed even though the ‘stamp’ is there? Also, did you read the documentation we have on this subject? Was anythin
Hi I have a few questions regarding this solution that I hope can be answered in this thread. DocMan-event action versus Report Rule Engine. Are the two to be considered as two different ways of triggering the digital sign. functionality. Where the DocMan-event actions is done if using Document Approval and report rule engine for any report that we want to be signed? Certifications When testing this functionality (both running the code ‘ifsapp.Edm_File_Sign_Util_API.Certify_Pdf_File’ as well as setting up Report Rule Engine) the result is that the message: “Dokumentcertifieringens giltighet är OKÄND. Författaren gick inte att verifiera” shows. Q1: Does this mean that the end-customer has to purchase certificates from a source that Adobe has listed as ‘Trusted’? If so, then the ’Generate Self-signed Certificate’ in KeyStore will not come into play? Q2: Are there any guidelines or recomendations on this from IFS-side? How has this been handled at other customers using this functionalit
Hi Addovation has a solution for this for App9 (Upd5) and onwards. So it might not help you in the current IFS-installation but for the future it might be something to look in to. https://www.youtube.com/watch?v=yZnGEb2UhyU Regards Gustaf
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
