Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Sandman0724JFW opened this issue Sep 26, 2023 · 12 comments

Comments

@Sandman0724JFW
Copy link

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
Copy link

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
Copy link
Member

Tiliavir commented Oct 6, 2023

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
Copy link

jayrod0112 commented Oct 11, 2023

@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
Copy link

@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
Copy link
Author

Hi @Tiliavir,

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

@naveenabn
Copy link

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
Copy link

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

@Maledives
Copy link

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
Copy link
Member

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
Copy link

naveenabn commented Nov 20, 2023 via email

@jayrod0112
Copy link

@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
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants