Security console has no safeties against multiple runs #373
Labels
importance: may
Purely optional, nothing important happens if not done
internal
Without much influence on the interface
security
A security issue, be it a bug or design problem
The security console commands (
rbac/*
) can be ran any number of times, and the only safeties that prevents repeated runs from causing a mess are database integrity constraint violation checks - hardly a pretty or reliable solution.Add a simple migration-like system on this mechanism:
rbac/*
command was ran via a database tableThis does not entail any rollbacks or anything like this - this is a simple safety system, not a complete system.
The text was updated successfully, but these errors were encountered: