socialize.setUID

Security Requirements

The Gigya service supports a mechanism to verify the authenticity of the setUID call. This mechanism is used to prove that the call is in fact coming from your site, in order to prevent fraud.

We require every setUID call to be signed using a HMAC-SHA1 signature. The "UIDSig" parameter (see table of parameters below) is defined for this objective, and is a required parameter. Gigya will verify the authenticity of the signature to prove that it is in fact coming from your site and not from somewhere else.

Follow the instructions in Constructing a Signature to set the UIDSig parameter of the setUID call, and make the API call as soon as possible after that to prevent the signature from expiring.

Syntax

gigya.socialize.setUID(params)

Method Parameters

The following table lists the params object members:

Response Object Data Members

// Note: the actual signature calculation implementation should be on server side
function createSignature(UID, timestamp) {
       return '';
}

var dateStr = Math.round(new Date().getTime()/1000.0);  // Current time in Unix format 
                                                         // (i.e. the number of seconds since Jan. 1st 1970)
var siteUID= 'uTtCGqDTEtcZMGL08w';  // siteUID should be taken from the new user record
                                                   // you have stored in your DB in the previous step
var yourSig = createSignature(siteUID, dateStr);

var params = {
    siteUID: siteUID,
    timestamp:dateStr,
    UIDSig:yourSig
};

gigya.socialize.setUID(params);