Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

intent: a print feeder endpoint (<Name>PrintFeeder/{id}) has no role gate - a user with no role reads any document

Open
#7,921 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
47/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
api, backend, security

Research direction

Start with PrintFeeder.java.template and compare its generated GET endpoint with the REST controller’s read gate and PermissionSupport, including how access.extraRoles and extraRolesReadOnly are applied. Check the related work in #7913 and the tests for feeder authorization and nonexistent IDs. Done means unauthorized callers receive 403 before the root record is loaded, with the open question about related-node permissions resolved and covered.

Written by the indexing model from the issue text.

Description

Problem

The class generated for a print feeder, gen/events/<module>/<Name>PrintFeeder.java from PrintFeeder.java.template, serves GET .../<Name>PrintFeeder/{id} with no role gate. It has no @Roles and no in-code check. It loads the root record by id and returns it with its related records as JSON.

So any signed-in user, including one with no role at all, can read a document that the root entity's own REST controller refuses them with 403. The response is 200 with an empty body ({}) for an id that does not exist, so the endpoint also tells the caller which ids exist.

This was found next to #7913, which gates <Name>Generate/run and <Name>Transition/run. That fix deliberately stays to the two write endpoints.

Expected

The feeder demands the root entity's read gate, as PermissionSupport computes it for the controllers: the can: grants or the convention ReadOnly/FullAccess roles, with access.extraRoles and extraRolesReadOnly appended. A caller without it gets 403 before the root is loaded.

An open question is whether each related node (via a foreign key, possibly cross-model) should also demand its own read gate, or whether reading the document implies reading what it prints.

Dominant language
Java
Stars
278
Forks
97
Avg merge
18h 53m
Merged PRs (30d)
228

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-dirigible/dirigible

All issues in eclipse-dirigible/dirigible

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.