OpenProject API tokens depend on project membership to determine real access
OpenProject's API accepts session auth, personal tokens, OAuth 2.0, and external OIDC tokens, but a valid token only identifies the caller. What the caller can actually see or change is determined by their project memberships and roles. Inventories that record only token IDs miss the projects and work packages that make a credential risky. The article also warns that anonymous users may receive permissions on public projects unless authentication is required for all requests. It recommends testing tokens as members, non-members, and administrators, and revoking access promptly during offboarding.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in