spacebarchat / spacebarchat/server
Seating/user aliasing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 323
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 4
Description
There might be situations in which it is useful to write a message with a different sender than the user actually writing the message. In this case, a user aliasing mechanism could be used. Team users, account controllers and user groups may allow their members to write messages in behalf of respective teams/groups and/or other users controlled by themselves.
In order to act in behalf of somebody else, the delegate token granted by the /auth/alias API should be used as the authorisation token.
- /auth/alias
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 by locating the /auth/alias API entry point and reviewing how authorization tokens and users are represented. Clarify the supported aliasing relationships for team users, account controllers, user groups, and other users before implementation; done means the endpoint issues a delegate token that authorizes messages on behalf of the permitted identity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100