View Issue Details

This bug affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
03789Bug reportsOtherpublic2010-02-11 17:08
Reportermdekker Assigned Torakete  
PrioritynormalSeverityminor 
Status closedResolutionno change required 
Product Version1.86 
Summary03789: Create token
Description

It would be nice if there was a function to ask for a new token that creates a unique token and returns that token. This way a survey can be protected, and when needed by the remote application a token can be generated on the fly without the risk of having duplicates or the need to create another remote token table.

So the function would be sCreateToken (SurveyId) and it should return a token.

Additional Information

It is just an idea not really needed...

I can work around it by have a token table in my remote application and creating a unique token there, send the token to lsrc and use it. The only problem then is that a token could already be entered in limesurvey directly and then my remote application could create a duplicate token entry.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)0
I will donate to the project if issue is resolved
Browser
Database type & versiondna
Server OS (if known)dna
Webserver software & version (if known)dna
PHP Versiondna

Users monitoring this issue

There are no users monitoring this issue.

Activities

rakete

rakete

2009-12-15 09:18

reporter   ~10574

I use it like you do. Create a token Table on the remotesoftware and pass them to limesurvey.
To avoid the problems you mentioned I made and use the sTokenReturn function, which returns all unused tokens for a survey as csv.

But I see the point. By letting Limesurvey do the work and just give back the result, the Limesurvey integration developer have less work in some situations (like yours).

I keep that in mind for future improvements and let you know when something is ready for use...

c_schmitz

c_schmitz

2010-02-11 17:08

administrator   ~11044

Please move this to the idea tracker since it is a feature request.

Issue History

Date Modified Username Field Change
2009-10-23 16:25 mdekker New Issue
2009-10-23 16:25 mdekker Status new => assigned
2009-10-23 16:25 mdekker Assigned To => rakete
2009-10-23 16:25 mdekker LimeSurvey build number => 0
2009-10-23 16:25 mdekker Database & DB-Version => dna
2009-10-23 16:25 mdekker Operating System (Server) => dna
2009-10-23 16:25 mdekker Webserver => dna
2009-10-23 16:25 mdekker PHP Version => dna
2009-12-15 09:18 rakete Note Added: 10574
2010-02-11 17:08 c_schmitz Note Added: 11044
2010-02-11 17:08 c_schmitz Status assigned => closed
2010-02-11 17:08 c_schmitz Resolution open => no change required
2011-10-20 18:29 c_schmitz Category RemoteControl => (No Category)