You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since AuditRoleManager assumes, and enforces, a certain type and number of options relating to whitelisting, it's not possible to pass on RoleOptions instances with custom options. The culprit seems to be AuditWhitelistManager.
voidcreateRoleOption(RoleOptionsoptions)
{
if (options.getCustomOptions().isPresent())
{
thrownewInvalidRequestException("Whitelist options are not supported in CREATE ROLE statements");
}
Similar checks are done for alterRole.
The text was updated successfully, but these errors were encountered:
Right, ecAudit do put some restrictions on how the custom options are used. The one you mentioned, and some others in alterRoleOption().
The upside of doing this is that it is possible to feedback to the user if there is a typo in the option key. If we're ignoring unknown keys that means we're silently ignoring typos. But this may be something we have to sacrifice.
So, what level of ambition are we looking for here? Should the AuditRoleManger be able to wrap a custom IRoleManager? Or should we assume that "the other" IRoleManager will be "wrapping" the AuditRoleManager, in which case we only need to ignore unrecognized options?
Since
AuditRoleManager
assumes, and enforces, a certain type and number of options relating to whitelisting, it's not possible to pass onRoleOptions
instances with custom options. The culprit seems to beAuditWhitelistManager
.Similar checks are done for
alterRole
.The text was updated successfully, but these errors were encountered: