Search code examples
pythondjangotastypie

How to make sure that my AJAX requests are originating from the same server in Python

I have already asked a question about IP Authentication here: TastyPie Authentication from the same server

However, I need something more! An IP address could be very easily spoofed.

enter image description here

Scenario: My API (TastyPie) and Client App (in javascript) are on the same server/site/domain. My users don't login. I want to consume my API in my javascript client side.

Question: How can I make sure (authentication) that my AJAX requests are originating from the same server?

I'm using Tatypie. I need to authentication that the requests from the client are being made on the same server/domain etc. I cannot use 'logged in sessions' as my users don't login.

I have looked at private keys and generating a signature but they can viewed in the javascript making that method insecure. If I do it in a way to request a signature form the server (hiding the private key in some python code) anyone can make the same http request to get_signature that my javascript makes, thus defeating the point.

example get signature

I also tried to have the Django view put the signature in the view eliminating the need to make the get_signature call. This is safe, but means that I have to now refresh the page every time to get a new signature. From a users point of view only the first call to the API would work, after which they need to refresh, again pointless.

using Django for the signature

I cannot believe I'm the only person with this requirement. This is a common scenario I'm sure. Please help :) An example using custom authentication in Tastypie would be welcome too.

Thanks

Added:

Solution

  • Depending on your infrastructure @dragonx's answer might interest you most.

    my 2c

    You want to make sure that only if a client visits your website can use the api? Hmm does the bot, robot, crawler fall in the same category with the client then? Or am I wrong? This can be easily exploited in case you really want to secure it really.

    I cannot believe I'm the only person with this requirement.

    Maybe not, but as you can see you are prone to several attacks to your API and that can be a reason for someone not sharing your design and making security stricter with auth.

    EDIT

    Since we are talking about AJAX requests what does the IP part has to do with this? The IP will always be the Client's IP! So probably, you want a public API...

    • I would Go with the tokens/session/cookie part.

    • I 'd go with a generated token that lasts a little while and a flow described below.

    • I'd go with a limiter per some time, like Github does. Eg 60 requests per hour per ip or more for registered users

    To overcome the problem with the refreshing token I would just do this:

    1. Client visits the site

      -> server generates API TOKEN INIT

      -> Client gets API TOKEN INIT which is valid only for starting 1 request.

    2. Client makes AJAX Request to API

      -> Client uses API TOKEN INIT

      -> Server checks against API TOKEN INIT and limits

      -> Server accepts request

      -> Server passes back API TOKEN

      -> Client consumes response data and stores API TOKEN for further usage (Will be stored in browser memory via JS)

    3. Client Starts Comm with the API for a limited amount of time or requests. Notice that you know also the init token date so you can use it to check against the 1st visit on the page.

    The 1st token is generated via the server when the client visits. Then the client uses that token in order to obtain a real one, that lasts for some time or something else as of limitation. This makes someone actually visit the webpage and then he can access the API for a limit amount of time, requests perhaps etc.

    This way you don't need refreshing.

    Of course the above scenario could be simplified with only one token and a time limit as mentioned above.

    Of course the above scenario is prone to advanced crawlers, etc since you have no authentication.

    Of course a clever attacker can grab tokens from server and repeat the steps but, then you already had that that problem from start.

    Some extra points

    • As the comments provided please close writes to the API. You don't want to be a victim of DOS attacks with writes if you have doubts about your implementation(if not use auth) or for extra security
    • The token scenario as described above can also become more complicated eg by constantly exchanging tokens

    Just for reference GAE Cloud storage uses signed_urls for kind of the same purpose.

    Hope it helps.

    PS. regarding IP spoofing and Defense against spoofing attacks wikipedia says so packet's won't be returned to the attacker:

    Some upper layer protocols provide their own defense against IP spoofing attacks. For example, Transmission Control Protocol (TCP) uses sequence numbers negotiated with the remote machine to ensure that arriving packets are part of an established connection. Since the attacker normally can't see any reply packets, the sequence number must be guessed in order to hijack the connection. The poor implementation in many older operating systems and network devices, however, means that TCP sequence numbers can be predicted.