Remote Trigger - How the Token Authentication Works

When a link to the remote trigger is initiated from the Server, it sends a token id along with it. This token is a dynamic one so it is different for each request. The simulation server (or remote server) can validate this token back to the originating server. Once the user logs out or the system times out the token is rendered invalid and cannot be reused.

 


 

Using API with curl is easy. Here’s an example curl command that will provide a response when the token_id is passed.

$ curl http://developer.vlab.co.in/auth_token/?token_id-abcd1234  output :yes
 

If the provided token is a Valid Token*, the user gets a ‘yes’ response from the server.

*Valid Token= For Remote trigger(RT), a valid token is a token provided by the server.

This token is valid only during the time slot reserved for the RT experiment. Once the token is validated, the token becomes invalid for the rest of the requests.