[MDEV-10193] MariaDB Custom users Created: 2016-06-08  Updated: 2016-07-06  Resolved: 2016-07-06

Status: Closed
Project: MariaDB Server
Component/s: Authentication and Privilege System
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Blocker
Reporter: Srinivas Mutyala Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback


 Description   

Hi Team,

I would like to know how do we create following users in MariaDB ?

Security Officer (sso_role) : This user should only create other users, but shouldn’t have all other DBA privileges.
Emergency user ( root) : This user usually comes in to picture when there’s an emergency, otherwise any unauthorized access should lock this user as it’s a super user.
dba_readonly : This user should able do all DBA activities and read Databases, except any data manipulations.

Example : This is not working as expected for me.

GRANT

[ALTER,ALTER ROUTINE,CREATE,CREATE ROUTINE,CREATE TEMPORARY TABLES,CREATE VIEW,CREATE USER,DELETE,DROP,EVENT,EXECUTE,FILE,GRANT OPTION,
INDEX,INSERT,LOCK TABLES,PROCESS,PROXY,REFERENCES,RELOAD,REPLICATION CLIENT,REPLICATION SLAVE,SELECT,SHOW DATABASES,SHOW VIEW,SHUTDOWN,
SUPER,TRIGGER,CREATE TABLESPACE,UPDATE,USAGE]

ON .

TO 'sso_role'@'%'

IDENTIFIED BY 'password' ;

Thanks,
Srinivas



 Comments   
Comment by Srinivas Mutyala [ 2016-06-08 ]

I've already sent an email to : security@mariadb.org onThursday, June 02, 2016 5:24 PM, but no response till date and thus I've raised this ticket.

Comment by Sergei Golubchik [ 2016-06-08 ]
  1. I haven't seen any emails on security@ from this month. perhaps yours were caught up in the spam folder?
  2. This is not a support portal, but a public bug database. Do you think this behavior is a bug? Then, please, clarify what exactly behavior you believe is wrong and what should have it been instead. "Not working as expected" is not very helpful, sorry.
Comment by Elena Stepanova [ 2016-07-06 ]

If you have further information on this issue, please comment to re-open the report.

Generated at Thu Feb 08 07:40:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.