Access Control Tokens - Revision history

Mike.schofield at 09:41, 24 February 2011

2011-02-24T09:41:16Z

← Older revision		Revision as of 09:41, 24 February 2011
Line 1:		Line 1:
	'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.		'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.

	~~== Access Control Tokens ==~~		----

	''Permissions available to a SEM User for features within a SEM Module''		''Permissions available to a SEM User for features within a SEM Module''


			'''Access Control Tokens'''

	A SEM Module can have certain features made available to, or denied to, a user by use of "Access Control Token Settings"		A SEM Module can have certain features made available to, or denied to, a user by use of "Access Control Token Settings"

Mike.schofield at 10:28, 23 February 2011

2011-02-23T10:28:09Z

← Older revision		Revision as of 10:28, 23 February 2011
Line 5:		Line 5:
	''Permissions available to a SEM User for features within a SEM Module''		''Permissions available to a SEM User for features within a SEM Module''

	A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"		A SEM Module can have certain features made available to, or denied to, a user by use of "Access Control Token Settings"

	* Use the SEM menu option: "Managers" > "SEM Users" > "Tokens" to set the correct settings on a token.		* Use the SEM menu option: "Managers" > "SEM Users" > "Tokens" to set the correct settings on a token.

Mike.schofield at 16:44, 22 February 2011

2011-02-22T16:44:57Z

← Older revision		Revision as of 16:44, 22 February 2011
Line 32:		Line 32:
	#		#

	.... this will result in the following associative array being defined by the SEM framework ~~at the start of~~ the script:		.... this will result in the following associative array being defined by the SEM framework when the script is invoked:

	my %UserTokens = ();		my %UserTokens = ();

Mike.schofield at 12:30, 22 February 2011

2011-02-22T12:30:55Z

← Older revision		Revision as of 12:30, 22 February 2011
Line 20:		Line 20:


	'''		'''Reading Access Control Token Settings from within a Workstation Script'''
	Reading Access Control Token Settings from a Workstation Script'''


Line 62:		Line 61:
	push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\test\");		push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\test\");
	push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\crontab\"		push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\crontab\"


			If Token settings are required by a script that runs on an agent, then the token settings need to be read first by the "(M) Pre-processing" script (using the above technique) and then made available to the SEM Agent script by using the "[[ADD_SVR from a menu Pre-Process]]" technique.

Mike.schofield at 12:25, 22 February 2011

2011-02-22T12:25:30Z

← Older revision		Revision as of 12:25, 22 February 2011
Line 7:		Line 7:
	A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"		A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"

	Use the SEM menu option: "Managers" > "SEM Users" > "Tokens" to set the correct settings on a token.		* Use the SEM menu option: "Managers" > "SEM Users" > "Tokens" to set the correct settings on a token.

	Use the SEM menu option: "Managers" > "SEM Users" > "Profiles" to assign a token to a Profile.		* Use the SEM menu option: "Managers" > "SEM Users" > "Profiles" to assign a token to a Profile.

	Use the SEM menu option: "Managers" > "SEM Users" > "Accounts" to assign a Profile to a SEM User.		* Use the SEM menu option: "Managers" > "SEM Users" > "Accounts" to assign a Profile to a SEM User.

	Below is a screenshot of the Access Control Token for the SAgM Module:		Below is a screenshot of the Access Control Token for the SAgM Module:
Line 20:		Line 20:


			'''
	* Reading Access Control Token Settings from a Workstation Script		Reading Access Control Token Settings from a Workstation Script'''

Mike.schofield at 12:24, 22 February 2011

2011-02-22T12:24:18Z

← Older revision		Revision as of 12:24, 22 February 2011
Line 6:		Line 6:

	A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"		A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"

			Use the SEM menu option: "Managers" > "SEM Users" > "Tokens" to set the correct settings on a token.

			Use the SEM menu option: "Managers" > "SEM Users" > "Profiles" to assign a token to a Profile.

			Use the SEM menu option: "Managers" > "SEM Users" > "Accounts" to assign a Profile to a SEM User.

	Below is a screenshot of the Access Control Token for the SAgM Module:		Below is a screenshot of the Access Control Token for the SAgM Module:
Line 16:		Line 22:

	* Reading Access Control Token Settings from a Workstation Script		* Reading Access Control Token Settings from a Workstation Script


	Details of the "Access Control Tokens" that are available to the SEM Users (via the SEM Profile for this user) are available to all scripts that run on the SEM user's workstation.		Details of the "Access Control Tokens" that are available to the SEM Users (via the SEM Profile for this user) are available to all scripts that run on the SEM user's workstation.

Mike.schofield at 12:14, 22 February 2011

2011-02-22T12:14:36Z

← Older revision		Revision as of 12:14, 22 February 2011
Line 7:		Line 7:
	A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"		A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"

	Below is a screenshot of the Access Control Token for the SAgM		Below is a screenshot of the Access Control Token for the SAgM Module:


	[[File:SAgM Tokens.jpg]]		[[File:SAgM Tokens.jpg]]



Line 25:		Line 26:
	#		#

	.... this will result in the following associative array being defined by the SEM framework at ~~thestart~~ of the script:		.... this will result in the following associative array being defined by the SEM framework at the start of the script:

	my %UserTokens = ();		my %UserTokens = ();
Line 53:		Line 54:
	push(@{$UserTokens{"SAgM Agent Manager"}{"Scratch Groups"}}, "\tch\2");		push(@{$UserTokens{"SAgM Agent Manager"}{"Scratch Groups"}}, "\tch\2");
	push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\test\");		push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\test\");
	push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\~~junk~~\"		push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\crontab\"

Mike.schofield at 12:13, 22 February 2011

2011-02-22T12:13:16Z

← Older revision		Revision as of 12:13, 22 February 2011
Line 10:		Line 10:


	[[File:~~SAgM_Token~~]]		[[File:SAgM Tokens.jpg]]

Mike.schofield: Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. == Access Control Tokens == ''Permissions available to a SEM User for features within a SE..."

2011-02-22T12:06:51Z

Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. == Access Control Tokens == ''Permissions available to a SEM User for features within a SE..."

New page

'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.

== Access Control Tokens ==

''Permissions available to a SEM User for features within a SEM Module''

A SEM Module can have certain features made available or denied to a user by use of "Access Control Token Settings"

Below is a screenshot of the Access Control Token for the SAgM

[[File:SAgM_Token]]

* Reading Access Control Token Settings from a Workstation Script

Details of the "Access Control Tokens" that are available to the SEM Users (via the SEM Profile for this user) are available to all scripts that run on the SEM user's workstation.

If a script requires the Access Control Token Settings, then the following comment lines need to be added to the script that runs on the workstation:

#
# @{{INCLUDE_TOKENS
#

.... this will result in the following associative array being defined by the SEM framework at thestart of the script:

my %UserTokens = ();
#
push(@{$UserTokens{"SAgM Agent Manager"}{"Database Type"}}, "Microsoft Access");
$UserTokens{"SAgM Agent Manager"}{"Audit Browser"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Create Agent"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Copy Agent"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Modify Agent"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Update Agents"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Delete Agent"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Create Group"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Delete Group"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Title"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Address"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Port"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Connection"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Description"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Groups"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Icon"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Enabled"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Pingable"} = 1;
$UserTokens{"SAgM Agent Manager"}{"Variables"} = 1;
push(@{$UserTokens{"SAgM Agent Manager"}{"Reference Groups"}}, "\*ef\*1");
push(@{$UserTokens{"SAgM Agent Manager"}{"Reference Groups"}}, "\*ef\*2");
push(@{$UserTokens{"SAgM Agent Manager"}{"Scratch Groups"}}, "\*tch\*1");
push(@{$UserTokens{"SAgM Agent Manager"}{"Scratch Groups"}}, "\*tch\*2");
push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\*test\*");
push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\*junk\*"