Issue with setting page restrictions after Confluence 9.2 upgrade

[Connor]

I've recently upgraded our Confluence DC test environment from 8.5.23 to 9.2.5. After upgrading, I noticed a bug where we're unable to add new people to Page Restrictions. I can set a new restriction on a page, which will put me on the list of people who can view and edit. However, when I try to add a new person, then click apply, and then come back and view the list of people with view/edit access, that person is not on the list. 

I have engaged Atlassian support and we checked some things out including the network logs (which seems fine, all 200s) and checked the DB to ensure the restrictions are not showing up in there, but while they are reviewing the latest data I figured I would reach out to the community to see if anyone else has encountered this problem.

Thank you!

[pawarsachin84 · Accepted solution]

Hello @Connor ,

Thank you for your question! 😊

While it's difficult to provide a definitive answer without more information from Atlassian Support, here are some thoughts and potential things to explore, based on the problem description:

1. Permissions and user management

• User has correct groups and Space permissions.
• Check for user Directory Synchronization is working correctly. It is working as expected.

2. Upgrade-related issues

• A common cause of post-upgrade issues is incompatible plugins. Ensure that all installed plugins are compatible with your current Confluence 9.2.5 version.
• An issue like this could potentially be related to the Confluence index. Rebuilding the index from scratch might resolve the problem if the index is corrupted or incomplete.
• While the upgrade process handles schema changes, sometimes issues can arise. Check for any specific database schema discrepancies or inconsistencies related to permissions have been found in the DB.

Since Atlassian Support is actively working on your request, it's best to follow their guidance. They will likely be able to narrow down the cause and provide a solution based on their findings. 

[Connor]

Thank you for your response! I have confirmed that the directory sync is working and that space permissions are set appropriately as well. I have also upgraded all of my plugins as well as replicated the issue with the environment set in safe mode (all plugins disabled).

I think that the indexing is working properly, but I'm going to just rebuild the index just in case and see if that helps. Thank you for the suggestion. I will also see what I can find in the database. 

Thank you again!

[Connor]

@pawarsachin84 - reindexing the site fixed the problem immediately. I should have tried that! Thank you very much for your help, it is much appreciated.

[pawarsachin84]

Hello @Connor ,

I appreciate your confirmation that the problem has been fixed. It will assist our community members in comprehending the root cause of the problems.

I hope you have a wonderful day! 

[Calvin]

It does sound like Atlassian support is the best way to go. Random question though, are you using multiple servers/nodes? I'm wondering if you have it running over multiple nodes and there is some load balancing or authentication issues going on. If you try via an alternative clean browser or private brower and login again to ensure you authenticate, do you see any difference?

[Connor]

Hi Calvin, thank you for your response! We are running just a single instance deployment right now, and I have tested it out in a few different browsers in incognito/private sessions to no avail. Thanks again!