Databases
StackOverflow2013
Postsdbo
POAPI authentication using timestamp : What to do when the client's time setting is changed?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAPI authentication using timestamp : What to do when the client's time setting is changed?
    primarykey
    data
    text
    <p>I am implementing an REST API authentication system.</p> <p>I am basically using the method explained in this site:</p> <p><a href="http://www.thebuzzmedia.com/designing-a-secure-rest-api-without-oauth-authentication/" rel="noreferrer">http://www.thebuzzmedia.com/designing-a-secure-rest-api-without-oauth-authentication/</a></p> <p>Basically it uses the request body to create a hash, sends it to the server along with the actual request, the server recreates and compares it, and what not...</p> <p>I won't bother explaining the details. The important part is that <strong>I am using a timestamp</strong> in order to prevent "replay attacks".</p> <p>Quoting from the site, it explains:</p> <blockquote> <p>Compare the current server’s timestamp to the timestamp the client sent. Make sure the difference between the two timestamps it within an acceptable time limit (5-15mins maybe) to hinder replay attacks.</p> </blockquote> <p>The problem I am facing now is that <strong>if the client's clock setting is modified, it may cause unexpected API authentication failures, since the timestamp varies between the client and the server</strong>.</p> <p>Is there no way around this? Do I have to give up on using the timestamp?</p> <p>I would highly appreciate it if anyone can help me out with a solution for this timestamp problem, or with any other way which I can prevent replay attacks.</p> <p><strong>Note:</strong> I am aware that issuing a nonce to the client is an excellent way to prevent "replay attacks", but I want to make that my last resort, since the implementation cost of creating a nonce-issuing-API and the backend to manage the nonce is too large.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USashiina
    1. USashiina
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAPI authentication using timestamp : What to do when the client's time setting is changed?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAPI authentication using timestamp : What to do when the client's time setting is changed?
      1. USSatish
      1. VTFavorite
    3. VO
      singulars
      1. POAPI authentication using timestamp : What to do when the client's time setting is changed?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf the client's clock setting is modified frankly there will indeed be authentication failures and nobody can help except client has to investigate and rechange the settings. There are few things to really stop worrying about. Also 5-15mins is too large a acceptable limit. It should be +-60 seconds. Don't stop your idea of sending timestamp just for a irresponsible client. Your question is very good though.
      singulars
      1. POAPI authentication using timestamp : What to do when the client's time setting is changed?
      1. USSatish
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload