baloise / digital-signature

a digital signature confluence macro
https://marketplace.atlassian.com/1217404
Apache License 2.0
8 stars 8 forks source link

XML file does not appear to have any style information associated with it. The document tree is shown below #106

Open Sandman0724JFW opened 11 months ago

Sandman0724JFW commented 11 months ago

Confluence server v8.4.2 Digital-signature v7.0.4

I have 2 signature blocks added to the SIA template I’ve made and it’s looking great until I go to ‘sign’. I get this error: dig-sig-error

jayrod0112 commented 11 months ago

Hi. Is there an update with this issue? We are also having this issue after upgrading to v8.4. The only version available in Marketplace is Digital-signature v7.0.4.

Tiliavir commented 11 months ago

Hi @Sandman0724JFW

is the issue still existing or was it solved by a restart? Do you see any details in the server log?

@jayrod0112 we did release 7.0.7 just now.

jayrod0112 commented 11 months ago

@Tiliavir ; Thanks. The new version did enable us to have new signatures put in place.

However, the pages where the signatories have already placed their signatures, those signatures were cleared after installing version 7.0.7 and clearing plugin cache and restarting Confluence v8.4.0. These said pages now have pending signature status on them.

Would you be able to advise on this? Is there a way we can find which pages were affected? The page's version history is not helping as well.

jayrod0112 commented 11 months ago

@Tiliavir would you also be able to advise the table your app is using in Confluence? Is it one of the AO_* tables? We are trying to see if we can trace the missing signatures using the DB somehow.

Sandman0724JFW commented 11 months ago

Hi @Tiliavir,

It looks like the latest version resolves our issue. Thanks for your help!

naveenabn commented 10 months ago

Hi @Tiliavir ,

The pages where the signatories have already placed their signatures, those signatures were cleared after installing version 7.0.7 and clearing plugin cache and restarting Confluence v8.4.0. These said pages now have pending signature status on them.

Would you be able to advise on this? Is there a way we can find which pages were affected? The page's version history is not helping as well.

naveenabn commented 10 months ago

Hi @Tiliavir , please can you check and let me know

Maledives commented 10 months ago

Hi @Tiliavir , we have the same problem as @naveenabn. After we upgrade confluence to 8.5.2, all signatures (previous clicks) are gone in the control. Upgrading to 7.0.7 has caused signatures to reappear on some pages. Unfortunately not completely, as they are still completely missing on other pages.

Can you please check and give us a hint?

Thanks!

Tiliavir commented 9 months ago

Hi @naveenabn Hi @Maledives Hi @jayrod0112 Hi @Sandman0724JFW

the signatures are stored in the Bandana Cache. The key is a combination of page Id, user Id and the hashed text within the signature plugin. If the signatures are missing, it means the record is missing in the Bandana Cache. Can you rule out, that the content of the plugin was not changed in the mean time?

Otherwise you can read the Bandana Cache and check if there are keys that are not displayed.

naveenabn commented 9 months ago

Hi Markus,

Thanks for replying. Can we have a quick call on this to check along with you?. Can you be more specific what exactly we need to check?.

Regards, Naveen

From: Markus Lindenmann @.> Sent: 17 November 2023 14:20 To: baloise/digital-signature @.> Cc: Birudaraju, Naveen @.>; Mention @.> Subject: [EXTERNAL] Re: [baloise/digital-signature] XML file does not appear to have any style information associated with it. The document tree is shown below (Issue #106)

Caution: External Email - Report Suspicious Emails Using your Outlook Phish Button

Hi @naveenabnhttps://urldefense.com/v3/__https:/github.com/naveenabn__;!!GvhQE2RxWE86WUX9!_zJut0THbvNo4E1oBBSXcfdJW3KjqhVCXRprbLrLyNUvr2VZRyNzlLGtMqtI3JnOrSgoNJQ_kexYOi64_DFZS0Yv0B-Oj4W_EAkMZA$ Hi @Malediveshttps://urldefense.com/v3/__https:/github.com/Maledives__;!!GvhQE2RxWE86WUX9!_zJut0THbvNo4E1oBBSXcfdJW3KjqhVCXRprbLrLyNUvr2VZRyNzlLGtMqtI3JnOrSgoNJQ_kexYOi64_DFZS0Yv0B-Oj4X7h8EopA$ Hi @jayrod0112https://urldefense.com/v3/__https:/github.com/jayrod0112__;!!GvhQE2RxWE86WUX9!_zJut0THbvNo4E1oBBSXcfdJW3KjqhVCXRprbLrLyNUvr2VZRyNzlLGtMqtI3JnOrSgoNJQ_kexYOi64_DFZS0Yv0B-Oj4WcX8fdSg$ Hi @Sandman0724JFWhttps://urldefense.com/v3/__https:/github.com/Sandman0724JFW__;!!GvhQE2RxWE86WUX9!_zJut0THbvNo4E1oBBSXcfdJW3KjqhVCXRprbLrLyNUvr2VZRyNzlLGtMqtI3JnOrSgoNJQ_kexYOi64_DFZS0Yv0B-Oj4XKoVfmLw$

the signatures are stored in the Bandana Cache. The key is a combination of page Id, user Id and the hashed text within the signature plugin. If the signatures are missing, it means the record is missing in the Bandana Cache. Can you rule out, that the content of the plugin was not changed in the mean time?

Otherwise you can read the Bandana Cache and check if there are keys that are not displayed.

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/baloise/digital-signature/issues/106*issuecomment-1816513191__;Iw!!GvhQE2RxWE86WUX9!_zJut0THbvNo4E1oBBSXcfdJW3KjqhVCXRprbLrLyNUvr2VZRyNzlLGtMqtI3JnOrSgoNJQ_kexYOi64_DFZS0Yv0B-Oj4X_6FGFMw$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BDL6PYMBHKPZKNHYRLFN2OTYE5XABAVCNFSM6AAAAAA5IEFZFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJWGUYTGMJZGE__;!!GvhQE2RxWE86WUX9!_zJut0THbvNo4E1oBBSXcfdJW3KjqhVCXRprbLrLyNUvr2VZRyNzlLGtMqtI3JnOrSgoNJQ_kexYOi64_DFZS0Yv0B-Oj4VsMMjQUg$. You are receiving this because you were mentioned.Message ID: @.**@.>>

This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. For information about how we process data and monitor communications please see our Privacy Policy and for terms of use please see our Disclaimer both of which are available at www.abnamro.co.uk.

ABN AMRO Clearing Bank N.V. has its seat at Gustav Mahlerlaan 10 (1082 PP) Amsterdam, the Netherlands, and is registered in the Commercial Register of Amsterdam under number 33170459. ABN AMRO Clearing Bank N.V., London Branch has its UK registered office at 5 Aldermanbury Square, London EC2V 7HR and is registered at Companies House with branch registration number BR007553. ABN AMRO Clearing Bank N.V. is authorised and regulated by De Nederlandsche Bank and by the Financial Conduct Authority.

jayrod0112 commented 9 months ago

@Tiliavir , I can confirm that the record in the Confluence page was not changed after the Confluence upgrade. The plugin data on the affected pages have not been touched.

However, we did notice that the entry on the Bandana table has changed. Atlassian asked us as well to check the BANDANA table as they've identified this table when they've tried to replicate our issue (they are still reviewing the result of the query they've asked us to run in the BANDANA table).

Here is a sample entry of a page. Note that only the values on the bandanavalue column has changed. The format of how the column entry was written is different now. Also, the entries on the "signature" tag got cleared and there are now entries on the "missingSignatures" tag.

Confluence v7.19.6; digital-signature v7.0.4

image

Confluence v8.4.0; digital-signature v7.0.7 image

jayrod0112 commented 9 months ago

@Tiliavir .. Atlassian support has this to say after studying the contents of our BANDANA tables. Please advise if the data can still be retrieved.

... The suspicion here is that with the updated version of the app, it will migrate its BANDANA signature data from XML to JSON, and somewhere during the data migration process, the "signature" values aren't being correctly converted into expected JSON format, and are therefore dropped entirely.