Feature Request:
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Allow /api/externalTools to be CORS enabled
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Dataverse marketplace users.
What inspired the request?
To be able to install external tools from the marketplace we would need this endpoint to be reachable from an application like the marketplace.
What existing behavior do you want changed?
This endpoint blocks CORS
Any brand new behavior do you want to add to Dataverse?
Any open or closed issues related to this feature request?
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
Contributor 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.
Research direction
Start by locating the Java implementation of /api/externalTools and checking how CORS is configured for API endpoints. Reproduce the current blocked cross-origin request and run the relevant API tests. Done means marketplace-origin requests can reach this endpoint without regressing existing access controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100