Archived:Access Control System In Joomla 1.6 - Revision history

Tom Hutchison: Hutchy68 moved page Access Control System In Joomla 1.6 to Archived:Access Control System In Joomla 1.6: archiving

2013-05-27T13:49:12Z

Hutchy68 moved page Access Control System In Joomla 1.6 to Archived:Access Control System In Joomla 1.6: archiving

← Older revision	Revision as of 13:49, 27 May 2013
(No difference)

Wilsonge: Add version tag

2013-04-30T12:51:14Z

Add version tag

← Older revision		Revision as of 12:51, 30 April 2013
Line 1:		Line 1:
	{{archived\|34362\|Access Control List\|reason=This page has not been maintained in some time and no longer contains information relevant or current. Joomla! 1.6 is no longer supported.\|cat=Joomla! 1.6}}		{{version\|1.6}}{{archived\|34362\|Access Control List\|reason=This page has not been maintained in some time and no longer contains information relevant or current. Joomla! 1.6 is no longer supported.\|cat=Joomla! 1.6}}

Tom Hutchison: using new category inclusion

2012-11-29T13:45:17Z

using new category inclusion

← Older revision		Revision as of 13:45, 29 November 2012
Line 1:		Line 1:
	{{archived\|34362\|Access Control List\|reason=This page has not been maintained in some time and no longer contains information relevant or current. Joomla! 1.6 is no longer supported.}}		{{archived\|34362\|Access Control List\|reason=This page has not been maintained in some time and no longer contains information relevant or current. Joomla! 1.6 is no longer supported.\|cat=Joomla! 1.6}}

Tom Hutchison: archiving page

2012-11-28T15:30:45Z

archiving page

← Older revision		Revision as of 15:30, 28 November 2012
Line 1:		Line 1:
	{{~~RightTOC}}~~		{{archived\|34362\|Access Control List\|reason=This page has not been maintained in some time and no longer contains information relevant or current. Joomla! 1.6 is no longer supported.}}
	~~{{future~~\|~~1.6}}~~

	~~''Note:Please note that much of the information in this document is out of date.~~
	~~This is a pre alpha document Joomla! version 1.6 that shows early concepts~~
	~~not all of which are implemented in 1.6. Since version 1.6 is still under~~
	~~active development, screenshots and other information discussed in this~~
	~~article may change before the final release of version 1.6. However,~~
	~~it is expected that the basic concepts outlined here will not change.~~
	''


	~~==Overview==~~

	~~===Users===~~
	~~These are users stored in jos_users table. Please note that gid and usertype fields are only there for legacy purposes and are not used in the current ACL system.~~
	~~Users can be mapped to rules via jos_user_rule_map table.~~
	~~In phpGACL, users were called AROs (~~Access ~~Request Object).~~

	=~~==User Groups===~~
	These are user groups that are held in table jos_usergroups. You can have nested user groups. Each group obviously can hold an unlimited number of users and each user can be assigned to an unlimited number of user groups. These relations are held in the table jos_user_usergroup_map.
	~~User groups can be mapped to rules via the jos_usergroup_rule_map table.~~

	~~===Actions===~~
	~~Actions are things your users will perform such as logging in to backend.~~

	~~Actions have dependencies and precedence. For example, setting a group Admin rights will take precedence over lesser actions such as login. Thus, if a group~~ has ~~admin set to allow, you cannot deny them the ability to login.~~

	~~===Assets===~~
	~~Assets are items that you need to set access control on. For example each article on your site can be an asset and you can set edit permission for them. Currently these are~~ not ~~used~~ in ~~core.~~

	~~===Rules===~~
	~~Rules are combinations of actions~~ and ~~usergroups (~~or ~~users) and optionally assets~~.
	~~There are three types of rules:~~
	* Type 1~~: These are rules that allow a user or user group to do an action~~. ~~For example user group X can log in to backend.~~
	* Type 2: These are rules that allow a user or user group to do an action on an asset. For example user group X can edit an article with the id of Y.

	~~==Library==~~
	~~TODO~~
	~~==Examples==~~
	~~===Core Access Levels===~~
	~~There are three access levels in core by default: Public, Registered, Special. These are access levels. For them we use the action ''core.view''. Let's use '''Special''' for our example:~~
	First of all there is an asset group named Special. We need to tie some user groups to it and selecting Manager is enough. Because the system will automatically include its child groups (being Administrator and Super Administrator by default) The rule needed for this level is ''core.view.3''. As you remember naming convention is action_name.asset_group_id and here our id is 3.

	~~==Database tables==~~


	* jos_assets: id, parent_id, lft, rgt, level, name, title, rules
	* jos_usergroups: id, parent_id, lft, rgt, title
	* jos_user_usergroup_map: user_id, group_id
	* jos_viewlevels: id, title, ordering, rules

	* jos_categories and jos_content contain foreign key asset_id
	* Rules field is a JSON encoded string with content like this: '{"core.admin":{"7":1}~~,"core.manage":{"6":1~~}}'


	~~[[Category:Joomla! 1.6]]~~
	~~[[Category:Access Control]]~~
	~~[[Category:References]][[Category:Access Management]]~~

Elin: There is no reason to include outdated information on the wiki.

2011-01-12T10:55:59Z

There is no reason to include outdated information on the wiki.

← Older revision		Revision as of 10:55, 12 January 2011
Line 12:		Line 12:

	==Overview==		==Overview==


	~~===Sections===~~
	Sections are used to group rules, actions, assets and assetgroups for each extension using the table jos_access_sections. This allows us to have completely separate ACL systems for different extensions.

	===Users===		===Users===
Line 33:		Line 29:
	===Assets===		===Assets===
	Assets are items that you need to set access control on. For example each article on your site can be an asset and you can set edit permission for them. Currently these are not used in core.		Assets are items that you need to set access control on. For example each article on your site can be an asset and you can set edit permission for them. Currently these are not used in core.
	~~===Asset Groups===~~
	~~These are used for creating different view permissions for a combination of usergroups. (???)~~
	~~How this is achieved:~~
	* First a view action is created with access type 3. (eg. core.view)
	* Then an asset group is created with some user groups in it.
	* A rule is set with the name convention {action_name}.{asset_group_id} (eg. core.view.1 for Public)
	* action, assetgroup and user groups are all mapped to this rule.
	* When three of them map to the same rule then JUser::getAuthorisedLevels() will also return the new asset group id.

	===Rules===		===Rules===
Line 47:		Line 35:
	* Type 1: These are rules that allow a user or user group to do an action. For example user group X can log in to backend.		* Type 1: These are rules that allow a user or user group to do an action. For example user group X can log in to backend.
	* Type 2: These are rules that allow a user or user group to do an action on an asset. For example user group X can edit an article with the id of Y.		* Type 2: These are rules that allow a user or user group to do an action on an asset. For example user group X can edit an article with the id of Y.
	* Type 3: These are rules that allow a user or user group to do an action (mostly view) on an asset group. For example user group X can view articles with the asset group of Y. (???)

	==Library==		==Library==
Line 58:		Line 45:
	==Database tables==		==Database tables==

	~~It seems that this diagram has been deprecated in favor of much simpler structure.~~

	* jos_assets: id, parent_id, lft, rgt, level, name, title, rules		* jos_assets: id, parent_id, lft, rgt, level, name, title, rules
Line 68:		Line 54:
	* Rules field is a JSON encoded string with content like this: '{"core.admin":{"7":1},"core.manage":{"6":1}}'		* Rules field is a JSON encoded string with content like this: '{"core.admin":{"7":1},"core.manage":{"6":1}}'

	~~-- Matias 7-Mar-2010~~

	~~[[Image:Dia_acl_base.png]]~~

	[[Category:Joomla! 1.6]]		[[Category:Joomla! 1.6]]
	[[Category:Access Control]]		[[Category:Access Control]]
	[[Category:References]][[Category:Access Management]]		[[Category:References]][[Category:Access Management]]

Batch1211 at 08:59, 20 September 2010

2010-09-20T08:59:41Z

← Older revision		Revision as of 08:59, 20 September 2010
Line 74:		Line 74:
	[[Category:Joomla! 1.6]]		[[Category:Joomla! 1.6]]
	[[Category:Access Control]]		[[Category:Access Control]]
			[[Category:References]][[Category:Access Management]]

Betweenbrain: /* Actions */

2010-08-23T20:53:56Z

Actions

← Older revision		Revision as of 20:53, 23 August 2010
Line 28:		Line 28:
	===Actions===		===Actions===
	Actions are things your users will perform such as logging in to backend.		Actions are things your users will perform such as logging in to backend.

			Actions have dependencies and precedence. For example, setting a group Admin rights will take precedence over lesser actions such as login. Thus, if a group has admin set to allow, you cannot deny them the ability to login.

	===Assets===		===Assets===

Elin at 20:22, 23 August 2010

2010-08-23T20:22:11Z

← Older revision		Revision as of 20:22, 23 August 2010
Line 4:		Line 4:
	''Note:Please note that much of the information in this document is out of date.		''Note:Please note that much of the information in this document is out of date.
	This is a pre alpha document Joomla! version 1.6 that shows early concepts		This is a pre alpha document Joomla! version 1.6 that shows early concepts
	not all of which are implemented in 1.6. Since version 1.6 is still under		not all of which are implemented in 1.6. Since version 1.6 is still under
	active development, screenshots and other information discussed in this		active development, screenshots and other information discussed in this
	article may change before the final release of version 1.6. However,		article may change before the final release of version 1.6. However,
	it is expected that the basic concepts outlined here will not change.		it is expected that the basic concepts outlined here will not change.
	''		''

Elin at 20:21, 23 August 2010

2010-08-23T20:21:33Z

← Older revision		Revision as of 20:21, 23 August 2010
Line 3:		Line 3:

	''Note:Please note that much of the information in this document is out of date.		''Note:Please note that much of the information in this document is out of date.
	This is a pre alpha document Joomla! version 1.6 that shows early concepts not all of which are implemented in 1.6. Since version 1.6 is still under active development, screenshots and other information discussed in this article may change before the final release of version 1.6. However, it is expected that the basic concepts outlined here will not change.		This is a pre alpha document Joomla! version 1.6 that shows early concepts
			not all of which are implemented in 1.6. Since version 1.6 is still under
			active development, screenshots and other information discussed in this
			article may change before the final release of version 1.6. However,
			it is expected that the basic concepts outlined here will not change.
	''		''

Elin at 20:20, 23 August 2010

2010-08-23T20:20:06Z

← Older revision		Revision as of 20:20, 23 August 2010
Line 1:		Line 1:
	{{RightTOC}}		{{RightTOC}}
			{{future\|1.6}}

			''Note:Please note that much of the information in this document is out of date.
			This is a pre alpha document Joomla! version 1.6 that shows early concepts not all of which are implemented in 1.6. Since version 1.6 is still under active development, screenshots and other information discussed in this article may change before the final release of version 1.6. However, it is expected that the basic concepts outlined here will not change.
			''

	~~Please note that much of the information in this document is out of date.~~

	==Overview==		==Overview==