Model server sign-in for any provider, with member roles

Open
  • Is something wrong?
#36 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
authentication, authorization, backend-api-design

Research direction

Read packages/bim-sync/AUTHORIZATION.md and services/bim-authority/README.md first to understand the current contract. Trace how the model server verifies tokens and how the local stack handles sign-in. The issue is complete when it supports standard sign-in providers, provides viewer, editor, and manager roles per model, and uses the model server for local stack sign-in.

Written by the indexing model from the issue text.

Description

area: model-server help wanted

From the roadmap ("Next").

Today the model server verifies tokens from one configured sign-in service. To run on its own it needs:

  • sign-in for any standard provider;
  • built-in member roles per model: viewer, editor, manager;
  • the local stack's sign-in moved onto it.

See packages/bim-sync/AUTHORIZATION.md and services/bim-authority/README.md for the current contract.

Dominant language
TypeScript
Stars
85
Forks
10
Avg merge
1h 28m
Merged PRs (30d)
20

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from permitzip/mutinybim

All issues in permitzip/mutinybim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.