Attribute-level Security - Revision history

Ncgonz: /* haslevel */

2008-11-29T23:51:54Z

haslevel

← Older revision		Revision as of 23:51, 29 November 2008
Line 7:		Line 7:
	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">
	$securityMgr = &atkGetSecurityManager();		$securityMgr = &atkGetSecurityManager();
	if ($securityMgr->haslevel(1)		if ($securityMgr->haslevel(1))
	{		{
	//Do something		//Do something
	}		}
	</syntaxhighlight>		</syntaxhighlight>

	==Using tabs==		==Using tabs==
	When I asked on the mailing list, Ivo gave this idea as well:		When I asked on the mailing list, Ivo gave this idea as well:

Thomaspeschken: /* Using 'attrib level security' that is built into ATK */

2007-03-16T10:21:51Z

Using 'attrib level security' that is built into ATK

@@ Line 35: / Line 35: @@
 ==Using 'attrib level security' that is built into ATK==
-This one is something that needs a little research added here. Here is an subset of Ivo's comments on it:
+There is a feature called 'attrib level security' in atkSecurityManager,
-''There is a feature called 'attrib level security' in atkSecurityManager, but it's ages since I last used it so I'm not sure how it works. It involves an extra table where the rights per attribute are stored.''
+$config_security_attributes = true;
-''You should be able to find out the details by looking at atk/security/class.auth_db.inc. It has a method for retrieving the attribute privileges. It probably has some details about the table structure.''

bahtiar at 15:06, 14 January 2007

2007-01-14T15:06:29Z

← Older revision		Revision as of 15:06, 14 January 2007
Line 5:		Line 5:
	==haslevel==		==haslevel==
	A simple method is to wrap things around a haslevel check, e.g.		A simple method is to wrap things around a haslevel check, e.g.
	<~~pre~~>		<syntaxhighlight lang="php">
	$securityMgr = &atkGetSecurityManager();		$securityMgr = &atkGetSecurityManager();
	if ($securityMgr->haslevel(1) {		if ($securityMgr->haslevel(1)
			{
	//Do something		//Do something
	}		}
	<~~pre~~>		</syntaxhighlight>
	==Using tabs==		==Using tabs==
	When I asked on the mailing list, Ivo gave this idea as well		When I asked on the mailing list, Ivo gave this idea as well:

	A good alternative might be to spread the attributes over multiple tabs,		A good alternative might be to spread the attributes over multiple tabs,
	then add an access right that corresponds to the tabname, and setting it		then add an access right that corresponds to the tabname, and setting it
	up like so in your constructor:		up like so in your constructor:
	<~~pre~~>
			<syntaxhighlight lang="php">
	if ($this->allowed("advanced_tab")		if ($this->allowed("advanced_tab")
	{		{
Line 27:		Line 29:
	$this->add(....., "publication");		$this->add(....., "publication");
	}		}
	</~~pre~~>		</syntaxhighlight>
	You will obviously want to have a look into the allowed function in the API documentation
			You will obviously want to have a look into the allowed function in the API documentation.

	==Using 'attrib level security' that is built into ATK==		==Using 'attrib level security' that is built into ATK==

	This one is something that needs a little research added here. Here is an subset of Ivo's comments on it		This one is something that needs a little research added here. Here is an subset of Ivo's comments on it:

	There is a feature called 'attrib level security' in		''There is a feature called 'attrib level security' in atkSecurityManager, but it's ages since I last used it so I'm not sure how it works. It involves an extra table where the rights per attribute are stored.''
	atkSecurityManager, but it's ages since I last used it so I'm not sure
	how it works. It involves an extra table where the rights per
	attribute are stored.

	You should be able to find out the details by looking at		''You should be able to find out the details by looking at atk/security/class.auth_db.inc. It has a method for retrieving the attribute privileges. It probably has some details about the table structure.''
	atk/security/class.auth_db.inc. It has a method for retrieving the
	attribute privileges. It probably has some details about the table
	structure.

bahtiar at 05:38, 23 August 2006

2006-08-23T05:38:17Z

← Older revision		Revision as of 05:38, 23 August 2006
Line 1:		Line 1:
			{{Howto\|Advanced\|James Stewart}}

	Some times you want some people to see something that another group cannot.		Some times you want some people to see something that another group cannot.

bahtiar: Attribute Level Security moved to Attribute-level Security

2006-06-11T19:13:54Z

Attribute Level Security moved to Attribute-level Security

← Older revision	Revision as of 19:13, 11 June 2006
(No difference)

bahtiar: AttributeLevelSecurity moved to Attribute Level Security

2006-06-08T21:26:14Z

AttributeLevelSecurity moved to Attribute Level Security

← Older revision	Revision as of 21:26, 8 June 2006
(No difference)

Stootles at 23:44, 18 January 2006

2006-01-18T23:44:22Z

New page

Some times you want some people to see something that another group cannot.

==haslevel==
A simple method is to wrap things around a haslevel check, e.g.
<pre>
$securityMgr = &atkGetSecurityManager();
if ($securityMgr->haslevel(1) {
//Do something
}
<pre>
==Using tabs==
When I asked on the mailing list, Ivo gave this idea as well

A good alternative might be to spread the attributes over multiple tabs,
then add an access right that corresponds to the tabname, and setting it
up like so in your constructor:
<pre>
if ($this->allowed("advanced_tab")
{
$this->add(....., "advanced");
$this->add(....., "advanced");
}
if ($this->allowed("publication_tab")
{
$this->add(....., "publication");
}
</pre>
You will obviously want to have a look into the allowed function in the API documentation

==Using 'attrib level security' that is built into ATK==

This one is something that needs a little research added here. Here is an subset of Ivo's comments on it

There is a feature called 'attrib level security' in
atkSecurityManager, but it's ages since I last used it so I'm not sure
how it works. It involves an extra table where the rights per
attribute are stored.

You should be able to find out the details by looking at
atk/security/class.auth_db.inc. It has a method for retrieving the
attribute privileges. It probably has some details about the table
structure.