Access Control Tokens: Difference between revisions
No edit summary |
No edit summary |
||
| 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 | .... 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"}}, "\* | push(@{$UserTokens{"SAgM Agent Manager"}{"Modifiable Variables"}}, "\*crontab\*" | ||
Revision as of 12:14, 22 February 2011
'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 Module:
- 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 the start 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"}}, "\*crontab\*"
