How to verify after Upgrade
Asked by Ankit Rastogi:

Hi Team,

As we are planning to upgrade system to latest long term support release for **CVE-2022-26134.**

So I want to make sure all features/functionality works after upgrade so is there any way to validate confluence workings which make sure nothing breaks after upgrade.

Is there any backend way/APIs to verify Confluence .


Answers:
author: Srinatha T
body: HI [@Ankit Rastogi](/t5/user/viewprofilepage/user-id/2727884) ,

It depends on what all is configured in confluence and the amount of data in confluence. We do have some formal checks which are documented in the upgrade guide. You might want to check the upgrade guide below for more info.

* [Upgrading confluence](https://confluence.atlassian.com/doc/upgrading-confluence-4578.html)

Thanks,

Srinath T

comments: author: Ankit Rastogi
body: Great! Thanks [@Srinatha T](/t5/user/viewprofilepage/user-id/4686256)

At this link, mostly things related to do before and during the upgrade.

Can you please share the APIs details page? I was thinking to run APIs before and after the upgrade to compare responses and data. Let's see I have 100 pages on confluence and this count should be a response of some confluence API then I will run before and after the upgrade to compare this count. This is an example of one API but I want more API details that can help me to compare data/response.


author: Ankit Rastogi
body: And can you please share how we can create Personal Access Tokens (PAT) for Confluence 6.13.23 version


author: Srinatha T
body: Hi [@Ankit Rastogi](/t5/user/viewprofilepage/user-id/2727884) ,

Welcome to Atlassian community.

You will have to have a test environment to do the thorough test . You can refer to the release notes for info like what all is introduced/fixed but to make sure nothing breaks it is advisable to have clone setup of prod and do the upgrade there first and then moving to prod. That would be the most recommended way.

Thanks,

Srinath T

comments: author: Ankit Rastogi
body: Thanks [@Srinatha T](/t5/user/viewprofilepage/user-id/4686256)

We are going to do same by lower environment first.

But on lower environment or Prod after upgrade, I want to find what major thing we need to check/test Or what you recommend to test manually as well to make sure nothing is breaking? OR is there any backend way from API to validate?

Thanks in Advance.


author: Daniel Ebers
body: Hi [@Ankit Rastogi](/t5/user/viewprofilepage/user-id/2727884)
> Can you please share the APIs details page? I was thinking to run APIs before and after the upgrade to compare responses and data. Let's see I have 100 pages on confluence and this count should be a response of some confluence API then I will run before and after the upgrade to compare this count.

I think I understand what you mean. You want to do some tests again REST API to ensure the upgrade went fine and you want to do probably automated tests via REST API like commenting, create a page, deleting a page - basically understood, and a good idea.

However, there seems to be not much that is ready-made here, you can check though with documentation and write scripts to do the tests on your own.

* **Confluence Server REST API** <https://developer.atlassian.com/server/confluence/confluence-server-rest-api/>

Regards,  
Daniel


author: Daniel Ebers
body: Hi [@Ankit Rastogi](/t5/user/viewprofilepage/user-id/2727884)
> And can you please share how we can create Personal Access Tokens (PAT) for Confluence 6.13.23 version

Personal Access Tokens require Confluence version 7.9 (and later).

Please review:

* **Using Personal Access Tokens**   
  <https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html>

Regards,  
Daniel


Tags: confluence-server

cve-2022-26134

server