The database of the system OAuth-php is defined, but explained here the following relevant fields and fields that have been added to the original:
Stores the data of the application that we have created like service providers API. These are the main fields to take into account:
Field | Type | Null | Predetermined | Comments |
osr_id | int(11) | No | Auto numeric. Primary key | |
osr_usa_id_ref | int(11) | Sí | Application identifier | |
osr_consumer_key | varchar(64) | No | Key for the user. The one that we introduce in HP WallArt | |
osr_consumer_secret | varchar(64) | No | Secret key for the user, also for HP WallArt | |
osr_callback_uri | varchar(255) | No | URL of the application (our web) | |
osr_application_uri | varchar(255) | No | URL of the application (our web) |
This table stores each of the requests from HP WallArt Designer each time we launch the application. For that it is very important table. These are the most important fields. Two of them were added to the original table.
Field | Type | Null | Predetermined | Comments |
ost_id | int(11) | No | Auto numeric. Primary key | |
ost_osr_id_ref | int(11) | No | Application identifier of oauth_server_registry. By default it is 1 | |
ost_usa_id_ref | int(11) | No | Identifier of the logged user, from the table of users. | |
ost_usa_pro_ref | int(11) | No | Identifier of the project that we are editing. | |
ost_token | varchar(64) | No | Token returned from designer during project edition. | |
ost_token_secret | varchar(64) | No | Secret token returned from designer |
With these two tables we have all the main information about the data exchanged. Another table, oauth_log, is used to check how the operations are happening in the background. This will help monitor that every call between our web site and HP WallArt designer is happening in the right way.