mirror of https://github.com/opf/openproject.git synced 2026-06-14 03:30:14 +00:00

Files

T

Jan Sandbrink 4d305df714 Allow to use API Tokens as Bearer tokens

We generate those tokens with a prefix, so that we
can decide by looking at a token, whether it's an API Token
or a different kind of token, so that we can decide which
code path to choose for validating the token.

The usage of access tokens as Bearer token has the usability advantage,
that you can paste them as plaintext into tools that expect you
to specify the token as a header.

Also the Basic auth approach for our old tokens usually rather caused
issues, such as browsers prompting for credentials in surprising situations.
If we were to deprecate basic authentication one day, this change today could've
been the first step towards that.

2026-02-05 08:07:04 +01:00

client-libraries

lint fix

2024-04-29 17:13:24 +02:00

components

Merge pull request #21800 from opf/bug/70979-bug-api-v3-allows-reading-writing-internal-comments-when-the-enable-internal-comments-project-setting-is-disabled

2026-01-29 16:34:23 +03:00

example

create 8bit PNGs, reduce color palettes, max width 2000 px

2025-10-23 11:52:29 +02:00

paths

Remove workspace aliasing unless confirmed

2026-01-29 13:50:24 +03:00

README.md

API Version 3

Status: under development

The specification for the APIv3 is written according to the OpenAPI 3.1 Specification.

The file in the repository is split up into many files. Some OAS (OpenAPI Specification) do not support that. You can retrieve the complete, singular file from any OpenProject server under /api/v3/spec.json or /api/v3/spec.yml. Additionally, there is a script that outputs the specification as a whole as well, either as json or yaml depending on the given format argument:

./script/api/spec --format yaml > openproject-oas.yml