Improve Shiro logging
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Expected behavior
Authentication debugging info and errors should be available in WebAPI logs.
Actual behavior
We do not have enough debugging information about the authentication attempt, nor do we see the authentication errors. Only see it fails in Atlas.
Steps to reproduce behavior
Set up authenticated WebAPI, see no debug info. Set it up with faulty settings, you won't see the full error trace.
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
Start with the WebAPI authentication path and reproduce the issue using both valid authentication and faulty settings. Done means authentication debugging information and full authentication errors, including the error trace, are visible in WebAPI logs rather than only showing a failure in Atlas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100