David Harrington writes...
> The RADIUS management attributes are principal-specific.
> The principal-specific attributes can be found using
> securitymodel/securityname/securitylevel.
> isAccessAllowed already supports these fields.
Yes.
I think another way to frame Juergen's original comment is why the (augmented) VACM tables should useTSM in the securityModel field.
My answer was that it need not be restricted to TSM, but it would need to be restricted to some security model that was "dependent" on a RADIUS-aware transport model. Today, that means TSM.
