BMO/new-security-group - Revision history

Mcote: added Category:BMO using HotCat

2015-01-13T03:45:05Z

← Older revision		Revision as of 03:45, 13 January 2015
Line 14:		Line 14:
	** If the group is to be used as the default security group for a product, add the group to <tt>%product_sec_groups</tt>		** If the group is to be used as the default security group for a product, add the group to <tt>%product_sec_groups</tt>
	** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>		** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>

			[[Category:BMO]]

Glob: /* Adding a new security group */

2013-05-06T05:58:34Z

Adding a new security group

← Older revision		Revision as of 05:58, 6 May 2013
Line 1:		Line 1:
	== Adding a new security group ==		== Adding a new security group ==

	~~'''~~Creating the group~~'''~~		=== Creating the group ===

	* Security groups are rarely granted explicitly into. Normally the groups membership is determined by inheritance from other groups.		* 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.		* 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~~'''~~		=== 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:		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:		* 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)~~
	** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>		** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>

Glob: /* Adding a new security group */

2012-06-18T08:44:27Z

Adding a new security group

← Older revision		Revision as of 08:44, 18 June 2012
Line 13:		Line 13:
	** 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 (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"):
	*** Add the group to <tt>%product_sec_groups</tt> (this establishes the mapping)		*** 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>		** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>

Dlawrence at 15:10, 8 May 2012

2012-05-08T15:10:35Z

← Older revision		Revision as of 15:10, 8 May 2012
Line 1:		Line 1:
	'''~~Note:~~''' ~~Moved~~ to ~~https://wiki~~.~~mozilla~~.~~org/BMO/Requesting_Changes#Security_Groups~~		== Adding a new security group ==
	~~Edit there instead~~
			'''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.

	~~== Adding a new security group ==~~		'''Code changes'''

	These steps need to be implemented when adding a new "security" group to BMO after the group has been created on BMO:		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:		* Add code to extensions/BMO/lib/Data.pm that accomplish the following:
Line 11:		Line 15:
	*** Add the group to <tt>%always_fileable_group</tt> (this ensures all users can file bugs into this group)		*** 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>		** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>

	* Security groups are rarely granted explicitly into. Normally the groups membership is determined by inheritance from other groups.

Dlawrence at 21:10, 7 May 2012

2012-05-07T21:10:42Z

← Older revision		Revision as of 21:10, 7 May 2012
Line 1:		Line 1:
			'''Note:''' Moved to https://wiki.mozilla.org/BMO/Requesting_Changes#Security_Groups
			Edit there instead

	== Adding a new security group ==		== Adding a new security group ==

Dlawrence at 14:42, 2 May 2012

2012-05-02T14:42:52Z

← Older revision		Revision as of 14:42, 2 May 2012
Line 9:		Line 9:
	** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>		** 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.		* Security groups are rarely granted explicitly into. Normally the groups membership is determined by inheritance from other groups.

Glob at 07:31, 2 May 2012

2012-05-02T07:31:51Z

← Older revision		Revision as of 07:31, 2 May 2012
Line 1:		Line 1:
	== Adding a new security group ==		== Adding a new security group ==

	These steps need to be implemented when adding a new "security" group to BMO:		These steps need to be implemented 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:		* Add code to extensions/BMO/lib/Data.pm that accomplish the following:
	** ~~%group_to_cc_map: Add~~ the ~~email address~~ to ~~automatically CC when a bug is placed in~~ the security group.		** 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"):
	** %~~always_fileable_group:~~ Add the group ~~as one that~~ can ~~always be filed~~ into~~, whoever you are.~~		*** Add the group to <tt>%product_sec_groups</tt> (this establishes the mapping)
	** ~~%product_sec_groups: Add~~ the ~~product to group mapping for~~ the ~~new security~~ group.		*** 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.		* Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.

Dlawrence: /* Adding a new security group */

2011-09-30T21:14:26Z

Adding a new security group

← Older revision		Revision as of 21:14, 30 September 2011
Line 1:		Line 1:
	= Adding a new security group =		== Adding a new security group ==

	These steps need to be implemented when adding a new "security" group to BMO:		These steps need to be implemented when adding a new "security" group to BMO:

	1. Add code to extensions/BMO/lib/Data.pm that accomplish the following:		* Add code to extensions/BMO/lib/Data.pm that accomplish the following:
	a. %group_to_cc_map: Add the email address to automatically CC when a bug is placed in the security group.		** %group_to_cc_map: Add the email address to automatically CC when a bug is placed in the security group.
	b. %always_fileable_group: Add the group as one that can always be filed into, whoever you are.		** %always_fileable_group: Add the group as one that can always be filed into, whoever you are.
	c. %product_sec_groups: Add the product to group mapping for the new security group.		** %product_sec_groups: Add the product to group mapping for the new security group.
			* Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.
	2. Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.

Dlawrence: Created page with "= Adding a new security group = These steps need to be implemented when adding a new "security" group to BMO: 1. Add code to extensions/BMO/lib/Data.pm that accomplish the fol..."

2011-09-30T21:12:01Z

Created page with "= Adding a new security group = These steps need to be implemented when adding a new "security" group to BMO: 1. Add code to extensions/BMO/lib/Data.pm that accomplish the fol..."

New page

= Adding a new security group =

These steps need to be implemented when adding a new "security" group to BMO:

1. Add code to extensions/BMO/lib/Data.pm that accomplish the following:
a. %group_to_cc_map: Add the email address to automatically CC when a bug is placed in the security group.
b. %always_fileable_group: Add the group as one that can always be filed into, whoever you are.
c. %product_sec_groups: Add the product to group mapping for the new security group.

2. Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.