Authentication Overview

When a client website makes a read or write request to the warehouse’s web services, it is necessary to authenticate the request rather like a website requires you to log in before you can get full access to the site. The process of authentication might be described as checking you are who you say you are. In most cases, authentication will be followed by a process of authorisation, in other words granting you access to only things you are authorised to see. The web services in Indicia restrict access to the data content on a client website basis, therefore the purpose of authentication is to check that web service requests are coming from the correct website. To gain access to the web services requires the request to be authenticated using the website ID and password created when the client website was registered on the warehouse. In an ideal world a secure connection would be used so that the password can be passed between the client and server to authenticate. Secure communications over the internet normally depend on using a secure socket layer (SSL) - this is the industry standard technology in use when you visit sites such as online payment sites with the website’s protocol set to https. SSL connections require additional configuration on the server so, in Indicia, we cannot rely on it being an option. Therefore we had to design the web services so that they are secure even across an insecure connection.

If you aren’t interested in the technical details of the authentication process the you can skip to Authentication using the Client Helpers.

Nitty Gritty

Instead of https, Indicia uses digest authentication which is a protocol for authentication that does not require the password to be sent from the client to the server. This involves the following steps.

  1. The client requests a public token from the server, known as a nonce.

  2. The server generates the nonce and returns it to the client.

  3. The client combines the nonce with the password and then hashes this combined token using a non-reversible algorithm.

  4. The client sends this hashed token, known as an auth token with the public token when performing the web-services request which is to be kept secure.

  5. The server receives the request and combines the public token with the expected password, then hashes it using the same algorithm as the client.

  6. This hashed token is compared with the one sent from the client to determine if the client has sent the correct token and therefore knows the password. It also checks that the public token was issued recently and has not already been used, preventing the same authentication tokens from being sniffed and then re-used. Note that at no point does the password get sent across the connection so this approach is safe for insecure connections to web services.


The term nonce is derived from the notion of a number n which is used only once, hence n-once or nonce.