Skip to content

Instance admin feature#1769

Draft
seb-kw wants to merge 49 commits into
mainfrom
feature/instance-admin
Draft

Instance admin feature#1769
seb-kw wants to merge 49 commits into
mainfrom
feature/instance-admin

Conversation

@seb-kw
Copy link
Copy Markdown
Member

@seb-kw seb-kw commented Mar 2, 2026

Ensure CleanupOrphanedRecordsSQL is also callable

Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
@seb-kw seb-kw changed the title Starts adding a instance admin feature Instance admin feature Mar 2, 2026
seb-kw added 4 commits March 2, 2026 18:49
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
@seb-kw
Copy link
Copy Markdown
Member Author

seb-kw commented Apr 10, 2026

Ensure that setting an admin for a sso org is covered

@seb-kw
Copy link
Copy Markdown
Member Author

seb-kw commented Apr 10, 2026

Watch out because of badge api as we would remove the admin token

@seb-kw
Copy link
Copy Markdown
Member Author

seb-kw commented Apr 11, 2026

Ensure to add a feature to change asset slugs

Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
@seb-kw
Copy link
Copy Markdown
Member Author

seb-kw commented May 5, 2026

We also need an admin authed endpoint that confirms a given org exists and return the owner email address of that org.

We additionally need an admin authed endpoint that returns for an owner all other orgs this owner owns.

@Hubtrick-Git
Copy link
Copy Markdown
Collaborator

maybe we should also be able to reset the admin session timer somehow

@Hubtrick-Git
Copy link
Copy Markdown
Collaborator

Hubtrick-Git commented May 12, 2026

  • Manage Admins (Add, revoke, list)
  • Change Asset Slugs manually
  • Get owner information about org (if exists)
  • Get orgs with owner role for user
  • Usage statistics

TODO

  • Disable Org Creation
  • Instance Statistics (Vulns, Components, etc)
    • Average Remediation time for vulns inside org
    • Average amount of open vulns per severity
    • Vuln Classification (total amount per severity)
    • Most vulnerable projects
    • Most vulnerable assets
    • Most vulnerable asset_versions
  • Cache Statistics !!!

TBD

  • Database dump (sanitized)

@Hubtrick-Git
Copy link
Copy Markdown
Collaborator

@seb-kw currently we pass a limit to the backend when we want e.g. the ecosystem package distribution inside an org. What about if we change the limit to a threshold (relative or absolute?). Instead of "give me the top 10", give me the top 95% or at least 1k components . What do you think about that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants