planetarium / planetarium/ArenaService
JWT Server
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1
- Forks
- 3
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
After discussing with the team, I received advice for a better approach than having users issue JWTs themselves.
Instead of users manually generating tokens, I will follow the standard structure where a JWT server issues tokens. However, the process for obtaining the token (similar to the login process in traditional web services) will involve users signing a specific random value with their private key and sending it.
This approach simplifies the process for users by eliminating the need to handle token issuance, expiration, and service-specific details themselves, making it as seamless as a typical web login.
Originally posted by @Atralupus in https://github.com/planetarium/ArenaService/discussions/33#discussioncomment-11744753
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
The issue describes a proposed JWT server and a private-key signing flow but names no files, tests, or entry points. Start by locating the authentication and token-issuance code, then clarify the protocol and acceptance criteria with the team before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100