Versions Compared

Old Version 11

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 12

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action manage-roles
                    -roles-parametersfile <roles_parameters.xml>
UNIX            ./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action manage-roles
                    -roles-parametersfile <roles_parameters.xml>

Table 9- 1 Elements of the Manage roles command

...

<root>
     <parameter name="action" value="add"/>
     <parameter name="role-name" value="role-name"/>
     <parameter name="role-scope" value="role-scope"/>
     <complex name="permissions">
          <parameter permission-type="permission-type" permission-operation="permission-operation"/>
          …additional permissions definitions
     </complex>
     <complex name="resources" [value="*"]> [<parameter [resource-information]/>
          …additional resources definitions ]
     </complex>
     [<complex name="nodes" [value="*"]>
          <parameter node-name="node-name"/>
          …additional nodes definitions
     </complex>]
</root>

Table 9- 2 Parameter values for Adding a new role

ParameterDescription
action

The action we wish to perform on the defined role.

Value: add.

role-name

Value: The name of the role to be added.

Mandatory: Yes

role-scope

The scope of the role the user wants to define the permissions on.

Value: technology, application, Tier, or instance. See Table 9-3 on page 111.

Mandatory: Yes

permissions

The permissions we wish to assign to this role.

Info

When assigning permission to a role all the dependencies of this permission are automatically assigned to the role as well (i.e. assigning MONITOR.WHAT_IF will automatically assign MONITOR.EXPLAIN as well).

Mandatory: Yes

permission-type

The permission type name we wish to assign to this role, for example: monitor.

Mandatory: Yes

permission-operation

The permission operation name we wish to assign to this role, for example: view.

Mandatory: Yes

resources

The resources the role permissions apply to.

Mandatory: Yes

resource-information

Resource information holds the information of the resource the permission is granted on. This information is derived from the role scope parameter, as shown in Table 9-3 on page 111.

Mandatory: Yes

nodes

This parameter is relevant only to ‘technology’ role scope. Use this parameter to define technologies permissions on specific nodes. If this parameter is not defined the technology permissions will apply on all nodes.

Value: Name of the node

Info

To define permission on all the resources of a specific type and all future resources as well (i.e. all instances), do not specify any resource information. Instead, define the resources value attribute as "*". To define permission on all the nodes do not specify any node name. Instead, define the nodes value attribute as "*".

Mandatory: No

Table 9- 3 Role scope parameters

Role scope parameterResource informationExample
technologytechnology-code: the technology code the permission should be granted on<parameter technology-code="OR"/>
environmentenvironment-name: the name of the application the permission should be granted on.

<parameter environment-name="Default"/>

Info

View permission can only be set on the application resource.


apptier

apptier-name: the name of the Tier the permission should be granted on environment-name: the name of the application the Tier belongs to.

<parameter apptier-name="Oracle" environment-name="Default"/>

instance

instance-name: the name of the instance the permission should be granted on.

technology-code: this parameter is optional, specifies the instance technology code. This parameter should be used if the instance name is not unique.

server-name: this parameter is optional, specifies the server the instance is installed on. If this parameter is specified the technology code parameter must be specified as well. This parameter should be used if the instance name and technology are not unique.

<parameter instance-name="ORCL" technology-code="OR" server-name="orcl-server"/>

...

Parameters specification

Table 9- 4 Parameter values for Deleting a role

...

Parameters specification

Table 9- 5 Parameter values for Editing a role

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action manage-users
                    -roles-parametersfile <users_parameters.xml>
UNIX            ./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action manage-users
                    -roles-parametersfile <users_parameters.xml>

Table 9- 6 Elements for the Manage users command

...

<root>
     <parameter name="action" value="add"/>
     <parameter name="user-name" value="user-name"/>
     {<parameter name="user-clear-password" value="clear-password"/> |
     <parameter name="user-encrypted-password" value="encrypted-password"/>}
     [<complex name="user-roles">
          <parameter role-name="role-name"/>
          …additional roles definitions
     </complex>]
</root>

Table 9- 7 Parameters for Adding a new user

...

Info

The ‘admin’ user cannot be deleted. The user activating this command cannot delete himself.

 

Table 9- 8 Parameters for Deleting a user

...

<root>
     <parameter name="action" value="edit"/>
     <parameter name="user-name" value="user-name"/> [<parameter name="user-new-name" value="user-new-name"/>] [{<parameter name="user-clear-password" value="clear-password"/> |
     <parameter name="user-encrypted-password" value="encrypted-password"/>}]
     [<complex name="user-roles">
          <parameter role-name="role-name"/>
          …additional roles definitions
     </complex>]
</root>

Table 9-9 Parameters for Editing a user

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action roles-export
                    -mode {users|roles|all}
                    [-output-file <file_name>]
UNIX            ./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action roles-export
                    -mode {users|roles|all}
                    [-output-file <file_name>]

Table 9- 10 Elements for Exporting users/roles

...

Windows    infra\bin\psin_cli.bat
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action permissions-summary
                    [-user-name <user_name>] [-output-file <file_name>]
UNIX            ./infra/bin/psin_cli.sh
                    -i3-user <user_name>
                    {-i3-encrypted-password <encrypted_password> | -i3-clear-password <clear_password>}
                    -action permissions-summary
                    [-user-name <user_name>] [-output-file <file_name>]

Table 9- 11 Elements for the User permissions summary

...

<user-permissions-summary user-name="usr1">
     <roles-permissions-summary>
          <role role-name="monitor default environment" role-scope="ENVIRONMENT"
               <permission>
                    <description>'Monitor.View' permission on the selected applications</description>
                    <permission-type>MONITOR</permission-type>
                    <permission-operation>VIEW</permission-operation>
                    <resource resource-type="ENVIRONMENT" environment-name="Default" />
                    <affected-instances>
                         <instance>
                              <instance-name>PIFA1000</instance-name>
                              <server-name>pifa1000</server-name>
                              <technology-code>SQ</technology-code>
                         </instance>
                         <instance>
                              <instance-name>H47_TEST</instance-name>
                              <server-name>poolhp3</server-name>
                              <technology-code>SP</technology-code>
                         </instance>
                         <instance>
                              <instance-name>H47_TEST2</instance-name>
                              <server-name>poolhp3</server-name>
                              <technology-code>SP</technology-code>
                         </instance>
                    </affected-instances>
               </permission>
          </role>
          <role role-name="monitor sql apptier" role-scope="APPTIER">
               <permission>
                    <description>'Monitor.View' permission on the selected Tiers</description>
                    <permission-type>MONITOR</permission-type>
                    <permission-operation>VIEW</permission-operation>
                    <resource resource-type="APPTIER" environment-name="Default" apptier-name="SQL Server" />
                    <affected-instances>
                         <instance>
                              <instance-name>PIFA1000</instance-name>
                              <server-name>pifa1000</server-name>
                              <technology-code>SQ</technology-code>
                         </instance>
                    </affected-instances>
               </permission>
               <permission>
                    <description>'Monitor.Execute' permission on the selected Tiers</description>
                    <permission-type>MONITOR</permission-type>
                    <permission-operation>EXECUTE</permission-operation>
                    <resource resource-type="APPTIER" environment-name="Default" apptier-name="SQL Server" />
                    <affected-instances>
                         <instance>
                              <instance-name>PIFA1000</instance-name>
                              <server-name>pifa1000</server-name>
                              <technology-code>SQ</technology-code>
                         </instance>
                    </affected-instances>
               </permission>
          </role>
          <role role-name="administrate sql instance" role-scope="INSTANCE">
               <permission>
                    <description>'Administrate.Execute' permission on the selected instances</description>
                    <permission-type>ADMINISTRATE</permission-type>
                    <permission-operation>EXECUTE</permission-operation>
                    <resource resource-type="INSTANCE" instance-name="PIFA1000" server-name="pifa1000" technology-code="SQ" />
                    <affected-instances>
                         <instance>
                              <instance-name>PIFA1000</instance-name>
                              <server-name>pifa1000</server-name>
                              <technology-code>SQ</technology-code>
                         </instance>
                    </affected-instances>
               </permission>
               <permission>
                    <description>'Administrate.Full Control' permission on the selected instances</description>
                    <permission-type>ADMINISTRATE</permission-type>
                    <permission-operation>FULL_CONTROL</permission-operation>
                    <resource resource-type="INSTANCE" instance-name="PIFA1000" server-name="pifa1000" technology-code="SQ" />
                    <affected-instances>
                         <instance>
                              <instance-name>PIFA1000</instance-name>
                              <server-name>pifa1000</server-name>
                              <technology-code>SQ</technology-code>
                         </instance>
                    </affected-instances>
               </permission>
               <permission>
                    <description>'Administrate.View' permission on the selected instances</description>
                    <permission-type>ADMINISTRATE</permission-type>
                    <permission-operation>VIEW</permission-operation>
                    <resource resource-type="INSTANCE" instance-name="PIFA1000" server-name="pifa1000" technology-code="SQ" />
                    <affected-instances>
                         <instance>
                              <instance-name>PIFA1000</instance-name>
                              <server-name>pifa1000</server-name>
                              <technology-code>SQ</technology-code>
                         </instance>
                    </affected-instances>
               </permission>
          </role>
     </roles-permissions-summary>
</user-permissions-summary>

 

Precise. Performance intelligence from click to storage. Learn more > >

...


...

IDERA Website | Products | Buy | Support | Community | About Us | Resources |

Legal