Subversion Repositories SmartDukaan

Last modification

• Rev 37406 2026-08-26 11:15:36
• Author: amit

• Log message:

  Vivo captcha: put the /verdict shared secret in the cron properties
  
  The token was only in run-cron.sh, which is not version-controlled. Rebuild the
  box or deploy elsewhere and it silently vanishes -- the verdict call is
  best-effort and swallows failures, so nothing would break loudly; training data
  would just quietly stop being collected. Properties travel with the build.
  
  dev and staging are deliberately empty: with no token CaptchaService skips the
  call entirely, so a local run cannot post verdicts to the live solver and
  pollute the training corpus.
  
  CAPTCHA_VERDICT_TOKEN in the environment still overrides this, so the token can
  be rotated without a rebuild.