Getting HTTP/404 for WebAPI/user/* routes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Expected behavior
Successful authentication.
Actual behavior
Failed authentication. It appears as though Atlas is getting HTTP/404 from WebAPI for the following routes:
WebAPI/user/meWebAPI/user/login/db
I can verify this by running a local curl against WebAPI (away from Atlas) and noticing that WebAPI is in fact giving HTTP/404 for these routes.
I have setup security with the security configuration documentation but ended up in this state and unsure how to troubleshoot further.
Steps to reproduce behavior
I'm am unsure how to repro this, as I follow the documented for security setup.
Any help is much appreciated!
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 security configuration documentation and the reported WebAPI/user/me and WebAPI/user/login/db routes. Reproduce the responses with the local curl check described in the issue, then compare the configured security setup with the route behavior. Done means these routes are available and authentication succeeds instead of returning HTTP/404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100