-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Own Priviliges in Version 6.1 ? #664
Comments
It's not possible yet. It's a known regression from v5. However, it's likely to comme back like this: acl:
FUNCTION:
inspect: ...
grant: ...
revoke: ...
privileges:
ro:
- type: EXECUTE
on: FUNCTION This new way of declaring acl allows to deduplicate execution of inspect. |
All right, thank you very much :) |
I have another question ... It is possible to specify a config for roles, such as the log_statement.
However, this config only works for static roles and not for LDAP roles How can I use this config for roles that are created with a ldapsearch command ? This possibility does not work: - description: "Search LDAP to create Superusers."
ldapsearch:
base: ...
roles:
- name: '{member.cn}'
options: SUPERUSER LOGIN
config:
log_statement: all
|
This may a bug, please open another issue with verbose logs. |
I have already looked in the logs, but there is nothing to see. When I run the config with a static role, I get the following:
But when I link the config to the ldapsearch as in the config above, there is no log_statement anywhere in the log. I don't know if this is the same for someone else |
Hello everyone,
is there a possibility to define own privileges in version 6.1 (like in version 5) ?
For example like this:
`privileges:
my_own_priv:
Thanks for help :)
The text was updated successfully, but these errors were encountered: