BuiltinUsers.KEY in setting table
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
curl -d @user.json -H "Content-type:application/json" "http://localhost:8080/api/builtin-users?password=xxxx&key=xxxx"
Usually parameters in setting table defined as ":ParameterName", so for BuiltinUsers.KEY it would be ":BuiltinUsers.KEY". but in that case settingsSvc.get(API_KEY_IN_SETTINGS) does not find the key and user get a message "Dataverse config issue: No API key defined for built in user management" After changing the key to "BuiltinUsers.KEY" in setting table the API works.
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 API_KEY_IN_SETTINGS and settingsSvc.get in the built-in user management API, then compare the key expected by the code with the key stored in the setting table. Reproduce the curl request from the issue and verify that the corrected setting allows the request to work without the API-key configuration error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100