Content
View differences
Updated by Niels Lindenthal about 6 years ago
In our release API we currently can not differentiate the Bitnami packages from other installation methods. I would like to enhance this to allow for better support of this distribution channel.
**Background infromation about our Release API:**
The Release API allows users of a self-hosted OpenProject application to check whether a new version of the Community Edition or Enterprise Edition has been released. The purpose of this function is to prevent defective or insecure OpenProject applications.
An update banner is displayed on the start page of the OpenProject application and on the administrator page for users with administrator rights. This banner is generated dynamically via a request to the Release API and ascertains the status and availability of a new version using anonymous installation data.
Accessing the Release API includes the following information in order to be able to display the availability of new versions:
1. The type of installation packets used: installation packets, docker, manual installation;
2. The current version of the application;
3. The database version;
4. Whether the installation includes an active Enterprise Edition.
The access also contains a random, unique identification code for the installation in order to avoid counting accesses twice.
No personal data is processed as part of the Release API banner. However, data such as the IP address as well as the type and version of the browser are stored as server logs for a maximum of 90 days on technical grounds.
In order to disable Release API access, uncheck the box under ‘Administration > System settings > General > Display update security badge’ or set the [configuration guideline](https://www.openproject.org/?page_id=8695) ‘s_ecurity\_badge\_displayed: false’._
**Background infromation about our Release API:**
The Release API allows users of a self-hosted OpenProject application to check whether a new version of the Community Edition or Enterprise Edition has been released. The purpose of this function is to prevent defective or insecure OpenProject applications.
An update banner is displayed on the start page of the OpenProject application and on the administrator page for users with administrator rights. This banner is generated dynamically via a request to the Release API and ascertains the status and availability of a new version using anonymous installation data.
Accessing the Release API includes the following information in order to be able to display the availability of new versions:
1. The type of installation packets used: installation packets, docker, manual installation;
2. The current version of the application;
3. The database version;
4. Whether the installation includes an active Enterprise Edition.
The access also contains a random, unique identification code for the installation in order to avoid counting accesses twice.
No personal data is processed as part of the Release API banner. However, data such as the IP address as well as the type and version of the browser are stored as server logs for a maximum of 90 days on technical grounds.
In order to disable Release API access, uncheck the box under ‘Administration > System settings > General > Display update security badge’ or set the [configuration guideline](https://www.openproject.org/?page_id=8695) ‘s_ecurity\_badge\_displayed: false’._