OWASP / OWASP/SecurityShepherd
Setup guide should start if core database can't be found
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
Describe the bug
If the database properties file exists but the core database doesn't, we currently get a server error. Instead, it should redirect to the setup page with cached db settings.
This is especially useful for puppetized deployments where the database properties file is created, but the database isn't.
To Reproduce
Steps to reproduce the behavior:
- Remove database properties file
- Delete database
- Use the setup wizard
- Delete database
- Server error
Expected behavior
Should show the setup wizard
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 following the issue's reproduction sequence: use the setup wizard, delete the database while retaining the database properties file, and observe the server error. Trace the setup-page decision for this missing core database case and verify that the setup wizard opens with the cached database settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100