...
Database Schema
The database schema for the database is below. It can also be found in the application is the user has attributesdatabase::read permission by going to menu: Admin -> Database -> List Tables, then clicking on the "attributes" table.
| No Format |
|---|
CREATE TABLE `attributes` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`org_id` int(10) unsigned NOT NULL DEFAULT '1',
`resource` varchar(200) NOT NULL DEFAULT '',
`type` varchar(200) NOT NULL DEFAULT '',
`name` varchar(200) NOT NULL DEFAULT '',
`value` varchar(200) 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=103 DEFAULT CHARSET=utf8 |
A typical entry looks as below.
| No Format |
|---|
id: 102
org_id: 1
resource: devices
type: device_type
name: Wireless Router
value: wireless router
edited_by: system
edited_date: 2000-01-01 00:00:00 |
the details button for the table.
API / Web Access
You can access the /attributes collection using the normal Open-AudIT JSON based API. Just like any other collection. Please see the API documentation for further details.
Access is provided as part of a roles permissions. Attributes is a standard resource and can have create, read, update and delete permissions.
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
...
...
...
...
...
...
...
...
...
Web Application Routes
...
...
...
...
...
...
...
...
see The Open-AudIT API documentation for further details.