Well Doron replied to me with another information here: https://bugzilla.redhat.com/show_bug.cgi?id=1067036#c1
I did not know of BZ 10382222 nor did anybody point me there. How to create it myself in 3.3, directly via the SQL Command? Is this safe on a 3.3.3-2 el6? See the attached SQL Am 26.03.2014 11:21, schrieb Itamar Heim: > > an admin role with login? why not? > i thought we even pre-created such a default read only role by now: > Bug 1038222 - [RFE] Read Only Admin role in AP > > (and you can create one yourself in 3.3 as well iirc) -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
Create or replace FUNCTION __temp_insert_read_only_admin_role() 1 RETURNS VOID 2 AS $procedure$ 3 DECLARE 4 v_ROLE_ID UUID; 5 BEGIN 6 v_ROLE_ID := 'DEF0000C-0000-0000-0000-DEF00000000C'; 7 8 DELETE FROM roles_groups WHERE role_id = v_ROLE_ID; 9 INSERT INTO roles(id,name,description,is_readonly,role_type,allows_viewing_children,app_mode) SELECT v_ROLE_ID, 'ReadOnlyAdmin', 'Read Only Administrator Role', true, 1, true, 1 10 WHERE NOT EXISTS (SELECT id,name,description,is_readonly,role_type 11 FROM roles 12 WHERE id = v_ROLE_ID 13 AND name='ReadOnlyAdmin' 14 AND description='Read Only Administrator Role' 15 AND is_readonly=true 16 AND role_type=1); 17 18 -- Allowing this role to login 19 INSERT INTO roles_groups(role_id,action_group_id) VALUES(v_ROLE_ID, 1300); 20 21 RETURN; 22 END; $procedure$ 23 LANGUAGE plpgsql; 24 25 SELECT __temp_insert_read_only_admin_role(); 26 DROP function __temp_insert_read_only_admin_role();
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
