Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[FR] Members management improvements (API/deactivation)

未關閉
#516 0 則留言 3 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
typescript

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

Feature

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

主要語言
TypeScript
星號
3.9k
分支
374
平均合併
21 小時 18 分鐘
30 天內合併 PR
39

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

sourcebot-dev/sourcebot 的其他 Issue

查看 sourcebot-dev/sourcebot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。