Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Code examples added

...

The Account Manager has three main Views:

  • Accounts: for the configuration of User Accounts
  • Masters: for configuring the JobScheduler Masters that can be accessed by a Role
  • Permissions: for configuring access to Folders and the Permissions for a Role

...

  • A role jocc_test had been added with potential access to all JobScheduler Masters.
    • Note that if no permissions are specified for this relationship then this configuration will be removed when the current user leaves the Managing Accounts view.
  • Two JobSchedulers Masters have been specified and roles specific to these JobSchedulers configured:
    • An api_test Role has been created whose permissions are restricted to the JobScheduler Master with ID jobscheduler_1.11.
      • This configuration writes the following to the shiro.ini file:

        Code Block
        languagetext
        [roles]
        ...
        api_test = jobscheduler_1.11:sos:products:commands:jobscheduler_master
        ...
    • The default application_manager Role has been configured prior to being given or losing permissions specifically for the jobscheduler_1.11_cluster.
      • This configuration writes the following to the shiro.ini file:

        Code Block
        languagetext
        [roles]
        ...
        application_manager = ... , \
        ..................... jobscheduler_1.11_cluster:sos:products:joc_cockpit:jobscheduler_master:view, \
        ..................... ..
        Note that if no such permissions are specified for this relationship then this configuration will be removed when the current user leaves the Managing Accounts view
        .

The Permissions View

The Permissions view is accessed by clicking on a Role in the Master view as indicated in the screenshot above.

...