An database table for storing one-time-use tokens is needed as per #2. See design specification in UC4.
The table to be designed has applications beyond that just in this particular UC, but our first use of it will be in this particular instance. One-time-use tokens provide us with a secure way of sending arbitrary information via an HTTP GET request by storing the GET data in our database, as opposed to in the URL itself.
Deliverable: Database SQL code export containing Structure of a table for storing one-time-use tokens saved to the Google Drive.
An database table for storing one-time-use tokens is needed as per #2. See design specification in UC4.
The table to be designed has applications beyond that just in this particular UC, but our first use of it will be in this particular instance. One-time-use tokens provide us with a secure way of sending arbitrary information via an HTTP GET request by storing the GET data in our database, as opposed to in the URL itself.
Deliverable: Database SQL code export containing Structure of a table for storing one-time-use tokens saved to the Google Drive.