The IDE opens for a Developer-only user with a 'Could not get export list' error dialog, because the shell polls the export list the Developer role may not read
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start with platform-core/ui/platform/shell.js, in the header directive's getExports() rejection handler, and check how LocaleService.onInit triggers the request. The issue gives the expected behavior: a Developer opening the IDE should not see an error dialog for the expected 403. Verify the change by opening the shell as a Developer and confirming the dialog no longer blocks the IDE.
Written by the indexing model from the issue text.
Description
Images
- Image:
dirigiblelabs/dirigible:15.1.0-java(sha256:dac354be94f21f222e88b81fd7fc6e68d9616ee7b4e12bcb1e9eef0465bd213f) - Reference:
dirigiblelabs/dirigible:15.1.0(sha256:449b8c948738a2bd7a4294a7bec1000a08bc1da1cd20f312f0e54383a7af325d) - same behaviour on both
Steps
- Create a user with only the Developer role:
POST /services/security/users {"username":"dev1","password":"...","tenant":"default-tenant","roles":["<DEVELOPER role id>"]}-> 201 - Open
/services/web/shell-ide/in a browser asdev1.
Observed
- The shell requests
GET /services/data/export-async/on boot ->403 {"status":403,"error":"Forbidden","message":"Forbidden","path":"/services/data/export-async/"} - Console:
Failed to load resource: the server responded with a status of 403 ()and{data: Object, status: 403, ...} - A modal error alert "Could not get export list - Please check the console log for more information." covers the IDE on every shell load; perspective buttons cannot be clicked until it is closed.
- As
adminthe same request answers 200 and no dialog appears.
Expected
A Developer opens the IDE without an error. The 403 is correct (export/import are ADMINISTRATOR + OPERATOR, see the HttpSecurityURIConfigurator javadoc, which also keeps the Database perspective's tools open to "the developers it was built for"), so the shell header should not poll the export list for a user who may not export, or should treat a 403 as "no exports" silently.
Where
platform-core/ui/platform/shell.js, the header directive's getExports() (called from LocaleService.onInit): its rejection handler shows dialogHub.showAlert({type: Error, title: "Could not get export list"}) for any failure, including 403.
Evidence
Screenshot of the IDE as the Developer user with the dialog over the Workbench; the request and console lines above were captured from the browser on both images.
- Dominant language
- Java
- Stars
- 278
- Forks
- 97
- Avg merge
- 15h 33m
- Merged PRs (30d)
- 301
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-dirigible/dirigible
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eclipse-dirigible/dirigible#8636 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eclipse-dirigible/dirigible#8548 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
eclipse-dirigible/dirigible#8354 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
eclipse-dirigible/dirigible#8238 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
eclipse-dirigible/dirigible#8232 ·
Maintainers usually reply within 1 day
All issues in eclipse-dirigible/dirigible
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
xerial/sqlite-jdbc#1515 ·
Maintainers usually reply within 1 day
-
Area/Configuration Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ballerina-platform/static-code-analysis-tool#217 ·
Maintainers usually reply within 1 day
-
bug severity-medium XS
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nikolas-charalambidis/facepalm-maven-plugin#291 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
OakLoaf/PluginUpdater#264 ·
Maintainers usually reply within 1 day
-
[Bug]: withStartupTimeout() changes the startup timeout of all containers that use the default wait strategyPossibly taken @aymenjamaaoui claimed this today. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
testcontainers/testcontainers-java#12171 ·
Maintainers usually reply within 1 day