View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
20121Bug reportsAuthenticationpublic2025-05-23 13:312025-05-26 15:31
Reporteralainl88 Assigned Totibor.pacalat  
PrioritynoneSeveritytext 
Status closedResolutionwon't fix 
Summary20121: Wrong alert on failed authentication with access code
Description

When the user uses a wrong access token, he gets the alert "The access code you have provided is either not valid, or has already been used."
It seems like this text is obsolete and should be replaced to "The access code you have provided is incorrect."

Steps To Reproduce

Steps to reproduce

Start a new survey with closed participants list. Enter a wrong access code.

Expected result

The user should see an alert that inform him that the code is not correct

Actual result

The alert "The access code you have provided is either not valid, or has already been used" is shown. It could lead to misunderstanding since the error is provided only when a wrong access code is used.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)6.14.0+250520
I will donate to the project if issue is resolvedNo
Browser
Database type & versionMariaDB
Server OS (if known)
Webserver software & version (if known)
PHP Version8.2

Users monitoring this issue

There are no users monitoring this issue.

Activities

DenisChenu

DenisChenu

2025-05-23 14:14

developer   ~82746

If i don't make error : we update this string for security issue : don't give more information than needed

The access code you have provided is either not valid is a correct sentence
alainl88

alainl88

2025-05-23 15:36

reporter   ~82749

Issued a PR https://github.com/LimeSurvey/LimeSurvey/pull/4293.
I updated the errormsg as suggested
DenisChenu

DenisChenu

2025-05-23 16:29

developer   ~82750

No : the whole sentence is OK ! Can be both : bad token or already used or invalid token.
tibor.pacalat

tibor.pacalat

2025-05-26 15:30

administrator   ~82764

I agree with Denis, nothing to do here. This is vague because of security.

Issue History

Date Modified Username Field Change
2025-05-23 13:31 alainl88 New Issue
2025-05-23 14:14 DenisChenu Note Added: 82746
2025-05-23 14:14 DenisChenu Bug heat 0 => 2
2025-05-23 15:36 alainl88 Note Added: 82749
2025-05-23 15:36 alainl88 Bug heat 2 => 4
2025-05-23 16:29 DenisChenu Note Added: 82750
2025-05-26 15:30 tibor.pacalat Note Added: 82764
2025-05-26 15:30 tibor.pacalat Bug heat 4 => 6
2025-05-26 15:31 tibor.pacalat Assigned To => tibor.pacalat
2025-05-26 15:31 tibor.pacalat Status new => closed
2025-05-26 15:31 tibor.pacalat Resolution open => won't fix