Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
When assigning provileges to the user that is used for monitoring, to fetch authentication data and for replication it would be convenient to be able to use database roles. As it stands, this only works if the role in question is the default role for the user in question. I suggest that the settings for user/password for servers and sservices, monittoruser/monitorpw for servers and replication_user and replication_password for the mariadbmon monitor are complemented with a similar role parameter. When a role is specified, the role in question would be anabled after connection, i.e. by running SET ROLE <rolename>.
Attachments
Activity
To start off, I think the use of roles for MaxScale grants is a very smart idea and we definitely should do that. All supported versions of MariaDB and even MySQL/Percona support them and shipping an "installation SQL script" with MaxScale would be very simple.
As for having a parameter for SET ROLE, what's the benefit compared to just doing SET DEFAULT ROLE on the database itself?
Using SET ROLE is useful as you might want to use different roles for
different purposes but with the same user, i.e. one role for monitoring,
one for authentication and one for replication. This is not critical but
a useful feature.
/Karlsson
When assigning provileges to the user that is used for monitoring, to fetch authentication data and for replication it would be convenient to be able to use database roles. As it stands, this only works if the role in question is the default role for the user in question. I suggest that the settings for user/password for servers and sservices, monittoruser/monitorpw for servers are complemented with a similar role parameter. When a role is specified, the role in question would be anabled after connection, i.e. by running SET ROLE <rolename>.