Table of Contents
*(Under Review for V2)
Introduction
The license endpoint allows you to track the number of licenses found on your devices..
...
A License entry can be created using the web interface if the current user logged in has a role that contains the licenses::create permission. Go to menu: Manage -> Licenses -> Create Licenses. Also can be created from the Licenses View, using the "Create+" button.
To create an entry to track your licenses you have to provide a name, an organization, the number of licenses acquired and the name of the software. On the field "Match String" you have to provide the name of the software that you want to track, you can use the percent sign (%) as a wildcard in the match_string.
View License Details
Go to menu: Manage -> Licenses -> List Licenses.
...
You can also edit or delete the licenses.
Database Schema
The database schema
...
can
...
be found in the application
...
is the user has database::read permission by going to menu:
...
Admin -> Database -> List
...
Tables, then clicking on
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
CREATE TABLE `licenses` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(200) NOT NULL DEFAULT '',
`org_id` int(10) unsigned NOT NULL DEFAULT '1',
`org_descendants` enum('y','n') NOT NULL DEFAULT 'y',
`purchase_count` int(10) unsigned NOT NULL DEFAULT '0',
`used_count` int(10) unsigned NOT NULL DEFAULT '0',
`description` text NOT NULL,
`match_string` text NOT NULL,
`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=4 DEFAULT CHARSET=utf8; |
A typical entry looks as below.
...
| theme | Eclipse |
|---|---|
| language | text |
...
the details button for the table.
API / Web Access
You can access the
...
collection using the normal Open-AudIT JSON based API. Just like any other collection. Please
...
see The Open-AudIT API documentation for further details
...
.
...
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 |
|---|---|---|---|---|---|---|---|
| POST | n | create | licenses::create | /licenses | Insert a new license entry. | licenses_create.json | |
| GET | y | read | licenses::read | /licenses/{id} | Returns a license details. | licenses_read.json | |
| PATCH | y | update | licenses::update | /licenses/{id} | Update an attribute of a license entry. | licenses_update.json | |
| DELETE | y | delete | licenses::delete | /licenses/{id} | Delete a license entry. | licenses_delete.json | |
| GET | n | collection | licenses::read | /licenses | Returns a list of licenses. | licenses_collection.json |
Web Application Routes
Request Method | ID | Action | Resulting Function | Permission Required | URL Example | Notes |
|---|---|---|---|---|---|---|
| GET | n | create | create_form | licenses::create | /licenses/create | Displays a standard web form for submission to POST /licenses. |
| GET | y | update | update_form | licenses::update | /licenses/{id}/update | Show the license details with the option to update attributes using PATCH to /licenses/{id} |
...