BMO/new-security-group: Difference between revisions

← Older edit

BMO/new-security-group (view source)

Revision as of 03:45, 13 January 2015

582 bytes added , 13 January 2015

m

added Category:BMO using HotCat

Mcote

Confirmed users

1,927

edits

@@ Line 1: / Line 1: @@
 == Adding a new security group ==
-These steps need to be implemented when adding a new "security" group to BMO after the group has been created on BMO:
+=== Creating the group ===
+* Security groups are rarely granted explicitly into. Normally the groups membership is determined by inheritance from other groups.
+* Most security groups have a related "-team" group that is used for actually granting people into. For example, noone is in the 'client-services-security' group directly. There is a 'client-services-security-team' group which is a member of the 'client-services-security' group. The individual users are placed directly into the 'client-services-security-team' group when needed. Therefore they get access to the other group as well through inheritance. Only the 'client-services-security' group should be actually visible on the bug report.
+* If the group is to be used as the default security group for a product (ie. it will be used when the user checks "Many users could be harmed by this security problem: it should be kept hidden from the public until it is resolved"), it must be set to '''Shown/Shown'''.
+=== Code changes===
+These steps need to be implemented by the admin when adding a new "security" group to BMO after the group has been created on BMO:
 * Add code to extensions/BMO/lib/Data.pm that accomplish the following:
-** If the group is to be used as the default security group for a product (ie. it will be used when the user checks "Many users could be harmed by this security problem: it should be kept hidden from the public until it is resolved"):
+** If the group is to be used as the default security group for a product, add the group to <tt>%product_sec_groups</tt>
-*** Add the group to <tt>%product_sec_groups</tt> (this establishes the mapping)
-*** Add the group to <tt>%always_fileable_group</tt> (this ensures all users can file bugs into this group)
 ** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>
-* Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.
+[[Category:BMO]]