How can we help you?

Advanced documentation search

Response Resume Tokens, Versions, and Idempotency

Product: FeraSurvey Topic: Administration and Security Versions: Applies to all documented versions Current
Written by user
Updated

Protect response continuity while preventing replay, duplicates, and lost updates.

Audience: Developers and security administrators
Editorial status: Public
Product: FeraSurvey

Overview

Protect response continuity while preventing replay, duplicates, and lost updates.

Key points

  • Resume tokens are stored for the matching public key.
  • Save and submit include expected response version.
  • Conflicts can return currentVersion and server data.
  • Idempotency keys identify a logical save, submit, or invitation send.
  • Tokens and keys must be scoped, expired, and excluded from logs.

Recommended procedure

  1. Classify the survey data and identity requirements.
  2. Choose the least permissive distribution and access model that meets the need.
  3. Protect links, tokens, exports, and integration secrets.
  4. Audit administrative actions and test isolation, retention, and recovery.

Troubleshooting

Sensitive data is exposed

Disable or rotate affected access, preserve evidence, and follow the incident procedure.

The policy is unclear

Keep the article in draft until product, engineering, security, and legal approve the contract.

Related documentation