Subversion Repositories SmartDukaan

Last modification

• Rev 37328 2026-08-17 19:25:56
• Author: amit

• Log message:

  Fetch a fresh EWB auth token when the cached one is stale
  
  Two defects made an expired EWB token unrecoverable, surfacing as GSP102
  "eInvoice AuthToken not found or expired" on every GET.
  
  1. ewbApiGet's retry was unreachable. NIC returns GSP102 with HTTP 400, and
  RestClient.execute throws GE_1005 on any non-2xx before returning the body, so the
  'if (response.contains("GSP102"))' branch could never run. A failed first attempt is
  now treated as a possibly-stale token and retried once with a freshly minted one; a
  second failure propagates. The POST path was unaffected — executeJson does not check
  status, so its retry already worked.
  
  2. Eviction targeted the wrong cache. The token is cached in redisCacheManager but all
  three sites evicted through redisFortnightlyCacheManage, a different cache, so the
  eviction was a silent no-op and the stale token survived. Eviction now goes through
  GstProAuthService.evictEwbAuthToken, declared beside the @Cacheable and pinned to the
  same cacheManager so the two cannot drift apart again.
  
  Found while dry-running the EWB backfill, which failed on the first invoice.