Versions Compared

Key

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

...

To add a new user to Open-AudIT you have to provide the details of that person, assign the organization, select the relevant Roles (multiple roles can be selected), select if the user is active or not, etc. In addition, you must grant permission to that user to access one or more organizations. It is important to notice that selecting a parent organization will automatically provide access to its children.


Image RemovedImage Added


Image AddedImage Removed

View Role Details

...

You will see a list of roles. You can view a role by clicking on the blue view icon. You can also edit or delete roles (except standard roles).

Image RemovedImage Added

 


Database Schema

The schema for the database is below. It can also be found in the application is the user has database::read permission by going to menu: Manage -> Database -> List, then clicking on the "roles" table.

Code Block
languagetext
themeEclipselanguagetext
CREATE TABLE `roles` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(200) NOT NULL DEFAULT '',
  `description` text NOT NULL,
  `permissions` text NOT NULL,
  `ad_group` varchar(100) NOT NULL DEFAULT '',
  `edited_by` varchar(200) NOT NULL DEFAULT '',
  `edited_date` datetime NOT NULL DEFAULT '2000-01-01 00:00:00',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8;

A typical entry looks as below.

Code Block
languagetext
themeEclipselanguagetext
         id: 1
       name: admin
description: This role can change global options.
permissions: {"attributes":"crud","baselines":"crud","configuration":"crud","database":"crud","errors":"r","groups":"crud","ldap_servers":"crud","logs":"crud","nmis":"crud","queries":"crud","reports":"r","roles":"crud","search":"crud","sessions":"crud","summaries":"crud","tasks":"crud"}
   ad_group: open-audit_roles_admin
  edited_by: system
edited_date: 2000-01-01 00:00:00

...

The API routes below are usable from both a JSON Restful API and the web interface. The Web application routes are specifically designed to be called from the web interface (a browser).

API Routes

Request Method
ID
Action
Resulting Function
Permission Required
URL Example
Notes
Example Response
POSTn
 

createroles::create/rolesInsert a new role entry.roles_create.json
GETy
 

readroles::read/roles/{id}Returns a role details.roles_read.json
PATCHy
 

updateroles::update/roles/{id}Update an attribute of a role entry.roles_update.json
DELETEy
 

deleteroles::delete/roles/{id}Delete a role entry.roles_delete.json
GETn
 

collectionroles::read/rolesReturns a list of roles.roles_collection.json

Web Application Routes

Request Method
ID
Action
Resulting Function
Permission Required
URL Example
Notes
GETncreatecreate_formroles::create/roles/createDisplays a standard web form for submission to POST /roles.
GETyupdateupdate_formroles::update/roles/{id}/updateShow the role details with the option to update attributes using PATCH to /roles/{id}

 

 

 

...