We encountered this problem during the last weeks.
The use case is:
Customer has installed the addon, then uninstalled it. Once the customer tries to install it again (from marketplace) - the 401 error occur.
From the last version of the addon we started to use atlassian-connect-spring-boot library for authentication (JWT Bearer token).
First install works, reinstall fails with 401 HTTP code.
We found out that:
- After we remove the record in the database, installation is possible again.
- Shared_secred column from the database is the same for all records
- Created_date and Last_modified_date has same values for a record
- Addon_installed fields is always with ‘TRUE’ value even if the user has uninstalled it
Has anyone encountered this kind of problem? What are the options to debug and learn more.
Thanks in advance.