Welcome, Guest
Username: Password: Remember me

TOPIC: Tokens are not unique

Tokens are not unique 1 year 9 months ago #82976

  • MPiet
  • MPiet's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 3
  • Karma: 0
I need some help with the tokens table.
We have several surveys running. We generate tokens each time we have a new person to invite.
Now I have noticed that the tokens are not unique!!!
Help, what has gone wrong?
How can I prevent this from happening?

I will for now start to use dummy tokens, because I don't want any more mix ups.

Help will be much appreciated.
The administrator has disabled public write access.

Re: Tokens are not unique 1 year 9 months ago #82978

  • lowprofile
  • lowprofile's Avatar
  • OFFLINE
  • Junior Lime
  • Posts: 22
  • Thank you received: 1
  • Karma: 0
I had the same problem with an older version , 1.90 or less, i cannot remember exactly. I will look at my old posting.
In my situation I had done imports of new tokens at different times . eg import 100 names/emails, generate tokens. Import another 100 names/emails generate tokens. and this second batch would randomly have tokens from the first generation. I also did not notice until it was in production, and to say this caused a problem for me is an understatement.

I am not sure if this still happens but I advise everyone who uses tokens to export the tokens and check them in excel (sort the token row then you highlight duplicate values)
Now if I have to add tokens to a running survey, I will take an existing token and randomly change some values or take a value from www.grc.com (perfect passwords)

which version are you on?
What OS is your server on?

I am not sure if it still happens in 1.92+, as I generate all tokens in the same run and then verify in excel.
I can also see that 1.92 does not allow you to use a duplicate token when generating them manually.
The administrator has disabled public write access.
The following user(s) said Thank You: MPiet

Re: Tokens are not unique 1 year 9 months ago #82980

  • DenisChenu
  • DenisChenu's Avatar
  • OFFLINE
  • Moderator Lime
  • Posts: 5866
  • Thank you received: 718
  • Karma: 222
lowprofile wrote:
I am not sure if it still happens in 1.92+, as I generate all tokens in the same run and then verify in excel.
I can also see that 1.92 does not allow you to use a duplicate token when generating them manually.
I just test with dummy token.
It's buggy : dummy token (1 caracter) => duplicate entry.

MPiet Please fill a bug report :).

Denis
Last Edit: 1 year 9 months ago by DenisChenu.
The administrator has disabled public write access.
The following user(s) said Thank You: MPiet

Re: Tokens are not unique 1 year 9 months ago #82993

  • MPiet
  • MPiet's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 3
  • Karma: 0
Thank you, I have just submitted the bug.
The administrator has disabled public write access.

Re: Tokens are not unique 1 year 9 months ago #82994

  • MPiet
  • MPiet's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 3
  • Karma: 0
Thank you very much for responding.
We use 1.91+ Build 12416
We don't generate all tokens in one batch, so I presume that is the problem.
We will continue by using random dummy codes, which I will then check in Excel for doubles.
For now it will do, so we are good to continue.
Hope it will be (or maybe allready is) fixed in later versions.
The administrator has disabled public write access.

Re: Tokens are not unique 1 year 8 months ago #84316

  • Surveying
  • Surveying's Avatar
  • OFFLINE
  • Fresh Lemon
  • Posts: 1
  • Karma: 0
I've encountered duplicate tokens in Version 1.92+ Build 120501.

Like MPiet, I was generating tokens and sending invitations in batches. I was using six character tokens and encountered 25 duplicates within the first 150. The sequence of these 25 tokens was identical, both sets were generated on the same day and within a few hours of each other. The invitations for the second set of 25 were sent out - the duplication wasn't picked up at that stage.

I can see that this issue has been fixed in Version 1.92+ Build 120425, but thought I should add that a similar thing seems to happen in Build 120501.
The administrator has disabled public write access.
Moderators: ITEd
Time to create page: 0.119 seconds
Donation Image