Feature Request: add ability to disable PrivateURL generation
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
UNC RDMC would like to add the ability to disable PrivateURL generation, at the collection level.
What kind of user is the feature intended for?
Curators, Depositors
What inspired the request?
We're launching a sensitive data repository which will be accessible to our entire campus. One of the primary security requirements is that all downloads must be traceable to a known user. Even though PrivateURLs only exist while a dataset is in DRAFT state, they're a share-able secret that may circumvent this requirement.
Are you thinking about creating a pull request for this feature?
We would like to, yes.
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 tracing where PrivateURLs are generated and how collection-level configuration is represented. Review the related security behavior and existing tests before deciding how the setting should interact with draft datasets. Done means selected collections can disable PrivateURL generation while existing behavior remains unchanged elsewhere, with coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100