Report hash issue

(2 posts) (2 voices)

Tags:

No tags yet.

  1. maron, Member

    Hi.

    I have 2 urls - see parameters below

    r=secret&u1=&u2=&u3=&u6=&p7=1299&p8=6426a1c290bf36aa447524f0741cfbe9&u9=&u10=&u11=&m=1&h=a5d55b00438067c1ed030d94c77e51d54d5de2ec

    r=secret&u1=&u2=&u3=&u6=&p7=1299&p8=07715deb2fdd183f9aa78c37a002d774&u9=&u10=&u11=&m=1&h=a5d55b00438067c1ed030d94c77e51d54d5de2ec

    p8 is a validation hash paremeter I'm using to validate the link to a publicly accessible report.

    The first link works fine but the second url fails with Report security hash does not match. Report execution aborted

    Can you see what I'm doing wrong?

  2. myDBR Team, Key Master

    See Generating a direct URL in the documentation.

    In short, myDBR report may have two kinds of user parameters: those that user can change and those that user cannot change. In order to protect the non-changeable parameters, a hash (h-parameter) is calculated to the report URL. A hash is calculated from secret seed value + all protected user parameters.

    In your URL you have number of user changeable parameters (the u-parameters) and two protected parameters (p7 and p8). As the p-parameter values differ from each other in the two URL's, the hash value should be different as well.

    What is the purpose of your own validation hash paremeter?

    --
    myDBR Team


Reply

You must log in to post.