[FR] Members management improvements (API/deactivation)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- typescript
- Área
- api, authentication, authorization
Línea de trabajo
No files, tests, or entry points are identified in the issue. Start by getting a maintainer decision on whether the scope is the admin API, activity-based management, or both; the work is ready to begin once the selected behavior and acceptance criteria are defined.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hey 👋
Context
We use Sourcebot EE, with a SSO login.
However, as SCIM is not available, old organization members are not deleted automatically, which may lead to security issues (they may not be able to log-in, but API key might still be active), as well as taking up seats for Sourcebot EE.
Deleting members must currently be done manually or through the DB directly.
Suggestion
As implementing LDAP/SCIM can be cumbersome, both for developers and Sourcebot administrators, here's some suggestions that provide a good compromise:
- Admin Members API: Create a admin-only REST API for user management (possibly related to #101?) that would:
- Allow admin scripts to list/disable/delete users
- Nice to have: Support batch operations for efficiently managing multiple users
- Nice to have: Properly documented with #101
- Activity-based User Management:
- Implement a configurable system to automatically disable users after a specified period of inactivity
- Allow administrators to set custom thresholds (30/60/90 days?)
- Nice to have: Users disabled through inactivity would be automatically re-enabled upon successful SSO login
- Nice to have: Include options to notify users before automatic disabling
Let me know what you think or if you need more details/context!
Cheers, Gabriel
- Lenguaje dominante
- TypeScript
- Estrellas
- 3.9k
- Forks
- 374
- Merge medio
- 21 h 18 min
- PR fusionados (30 d)
- 39
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de sourcebot-dev/sourcebot
-
bug triage needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
sourcebot-dev/sourcebot#1681 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
sourcebot-dev/sourcebot#1633 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
sourcebot-dev/sourcebot#1384 · 4 comentarios ·
-
ask_sb bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
sourcebot-dev/sourcebot#1137 · 4 comentarios ·
-
bug triage needed
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
sourcebot-dev/sourcebot#1661 · 1 comentario ·
Todos los issues de sourcebot-dev/sourcebot
Issues similares
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Crush Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
ElementsProject/cln-application#167 · 1 comentario · 1 reacción ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Quantco/pnpm-licenses#17 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100