Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Change WDK guest user creation mechanism

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java

Research direction

No files, tests, or entry points are named. Start by locating the Jersey filter that creates the persistent guest user and compare it with the newer service architecture. The issue needs an agreed design for endpoint-specific user requirements and the possible bearer-token model before implementation can be considered done.

Written by the indexing model from the issue text.

Description

enhancement

WDK has a Jersey filter that ensures there is always a user present for service request methods to use. If no registered user is logged in, this serves as a persistent guest user (attached to the session). Since the conversion to a client/service architecture, this method of providing users is overkill since not all services (in fact, many services) require a user or are user-agnostic (i.e. could use the "system user".

We should rework WDK to work more like our new service architecture, letting specific endpoints declare whether they need a user or not. This issue is to track ideas around this concept and may be related to the goal of factoring user authentication into a bearer token model, where WDK would simply be one of many services that respect VEuPathDB bearer tokens. It may even be a contributing reason to move WDK to the new service framework.

Dominant language
Java
Stars
1
Forks
4
Avg merge
1m
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VEuPathDB/WDK

All issues in VEuPathDB/WDK

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.