The (Qiskit)-token should not be stored in the DB.
Currently, it is required for the compilation (send via endpoints: selection/compiler-selection/qpu-selection ...) and at the same time stored in the DB for the later execution of analysis/compilation/qpu-selection results. Both via Qiskit-/Pytket-/Forest-Service (see Connectors in NISQ Analyzer).
It is actually (at least) stored in these tables:
analysis_job_input_parameters
analysis_result_input_parameters
compilation_result
qpu_selection_result
Instead, the token should not only be sent over the root endpoints (selection/compiler-selection/qpu-selection), but should also be sent over the corresponding execution-endpoints that also require the token to remove the DB dependency.
Therefore, first check again in which cases the token is currently taken out of the DB for processing.
Then, remove the token out of the respective tables and add it to the respective endpoints.
Note: Thereby, refreshToken or bearerToken is NOT meant as it is not stored in the DB - instead, the IBMQ token is meant, required to start an analysis, see, e.g., screenshot.
Note: Also the UI has to be updated, such that the token is added to the execution requests.
salmma
commented
1 year ago
The (Qiskit)-token should not be stored in the DB. Currently, it is required for the compilation (send via endpoints: selection/compiler-selection/qpu-selection ...) and at the same time stored in the DB for the later execution of analysis/compilation/qpu-selection results. Both via Qiskit-/Pytket-/Forest-Service (see Connectors in NISQ Analyzer). It is actually (at least) stored in these tables:
Instead, the token should not only be sent over the root endpoints (selection/compiler-selection/qpu-selection), but should also be sent over the corresponding execution-endpoints that also require the token to remove the DB dependency. Therefore, first check again in which cases the token is currently taken out of the DB for processing. Then, remove the token out of the respective tables and add it to the respective endpoints.
Note: Thereby, refreshToken or bearerToken is NOT meant as it is not stored in the DB - instead, the IBMQ token is meant, required to start an analysis, see, e.g., screenshot.
Note: Also the UI has to be updated, such that the token is added to the execution requests.