Recover a valid license without weakening verification


In 30 seconds
Problem
License state, notification delivery and installation identity must agree even when a worker or external service stops responding.
My part
I implemented licensing-service changes in Go and renewal recovery in the Rails application, including signed lease verification, tenant-scoped storage checks and a notification outbox.
Result
Renewal has independent recovery paths, while accepting a lease still depends on its signature and installation binding.
Technical decisions
Recover by requesting a new lease, never by bypassing verification.
- Why
- A stale local lease should not require weaker checks to recover.
- Trade-off
- Recovery still depends on a valid response from the licensing service.
Separate notification delivery from the domain transaction.
- Why
- An SMTP failure should be retried through a durable outbox.
- Trade-off
- The outbox needs deduplication and a worker to drain it.
Check storage through a constrained service.
- Why
- Tenant-driven bucket checks need SSRF protection, concurrency limits and an audit record.
- Trade-off
- Some checks are refused or delayed when the service cannot safely admit them.
Operation
I separated staging and production entitlements, corrected rejection-loop alarms for unknown keys and bounded installation queries. Toolchain updates followed published Go security advisories. The platform lease uses signature verification; the other products’ validation protocols are distinct.
Authorship
License Hub serves Setup products. I built the renewal integration in Conversa Labs’ proprietary modules on Chatwoot’s open-source (MIT) core.

