Issue Report: Server requires Authentication

Hi team, I want to report an issue related to our current survey setup in Kobo.

Summary
Our enumerators access the survey using a QR code we provide. The QR includes the login link, username, and password. When they scan the QR in the Kobo app, the app logs them in automatically and they start filling and submitting the survey. Until recently, the username and password in the link could be anything, because Kobo still accepted submissions even when the credentials were not real.

Chronology

  1. Our surveyors have been using the dummy login (embedded in the QR) without any problem.

  2. Yesterday the surveyors informed us that they were no longer able to submit their surveys. They still access the form, fill it in, and save drafts, but the submission fails when using the dummy credentials. (They reported that a notification appeared during submission)

  3. But when I tested the same process using the real username and password. The submission works.

  4. This confirms the issue is linked to Kobo now enforcing real login credentials for submissions.

Current concern
The QR method becomes risky. If we embed the real username and password in the QR code, enumerators will see our actual account credentials. This is not acceptable for access-control and data-security reasons.

Request
I need your help to clarify the following points.

  1. Did Kobo change the submission rule so dummy credentials are no longer accepted?

  2. Is there an alternative method that lets enumerators submit surveys without exposing the real login details?

  3. If QR-based auto-login is still supported, what is the correct way to configure it now so it stays secure?

If you need more information from our side, let me know and I will provide it.

Thanks.

@daydreamin, kindly please be informed that our team is working on a fix for this bug. We will update you once it is resolved.

1 Like

@Kal_Lam Thanks a lot for your quick reply!

I want to flag one thing on our side. We’re keeping the surveys in the Kobo app as drafts for now, so please also take extra care with any draft data stored on your end. We hope nothing happens to the draft files while the fix is in progress.

1 Like

Hello,
We are currently facing the same issue since morning.
Hoping this will be resolved soon.

@daydreamin, @biliyaminu, kindly be informed that the issue has now been resolved. Please feel free to reach out to us again if it persists. We sincerely apologize for the inconvenience caused.

@Kal_Lam Thank you for the update. I appreciate the quick follow-up.

Thanks again for the support!

1 Like

@daydreamin, :person_bowing: :folded_hands:

Hello,
We have the same problem on a self-hosted instance. When will this fix be available for deployment on our servers?
Best regards.

@mazzini, you may need to update your server to the latest patch release to fix this issue.