Create a docker-compose or other service-combination to allow userdb/oauth isolation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 4
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
SiteSearchData is a stand-alone WDK implementation that should not need to access our global OAuth server or any "real" Oracle user database to do its job. We could probably rig up a system that creates a containerized OAuth and/or userdb that can create and use user IDs in a completely independent value-space from our real user IDs. Possible implementations are containerized versions of OAuth and a postgres user DB. But even simpler may be a SQLite for user DB and an independently running OAuth with a dummy authenticator (and AtomicInteger counter to produce user IDs). Might be less work than it seems.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Compare the proposed containerized OAuth and PostgreSQL setup with the SQLite and dummy-authenticator alternative, then define how SiteSearchData gets an isolated user-ID space. Done means it operates without the global OAuth server or real Oracle user database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, java, postgresql, sqlite
- Domain
- authentication, databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100