David E Jones wrote:
In the design I'm working on, permissions can be granted to any
artifact that has a security element. Artifacts that don't have a
security element inherit permissions from artifacts higher up in the
hierarchy that do have a security element. This eliminates having to
name *everything* and instead you just name important security points.
What if a user finds their own "important security points" that we have
not already setup? Actually, I would argue that over time with enough
use nearly every screen, form, form field, service, and perhaps other
things would be designated as security points.
Why not just default to having anything and everything being a potential
security point and use tools and conventions to make it easier to
handle... but still totally flexible to configure externally (ie without
changing the code or configuration files, and without restarting the
system).
Those are good points. I'll update my document.
-Adrian
