RealDevSquad / RealDevSquad/website-backend
Documentation for Server to Server (S2S) Authorization
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
- The issue is to do a reading on how server-to-server authorization works, how microservices work, how services identify each other, and create documentation on s2s auth.
Expected Behavior
- The document should explain how server-to-server auth works and how it can be implemented for the requirement discussed.
Additional Information
- The requirement is to implement this server-to-server authorization on a portal which will act as a dashboard in RDS to rotate the keys and key management.
Checklist
- I have read and followed the project's code of conduct.
- I have searched for similar issues before creating this one.
- I have provided all the necessary information to understand and reproduce the issue.
- I am willing to contribute to the resolution of this issue.
- I have finished the documentation post reading
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
Start with the S2S authorization, microservices, service-identity, portal, and RDS key-rotation requirements stated in the issue; no files or tests are named. Define the documentation's implementation guidance and key-management scope, then verify it explains how services authenticate and how the proposed portal requirement is addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, backend, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100