Joomla WebCron Credential Synchronization Lifecycle
QCTNH keeps Joomla’s native WebCron credential synchronized through installation/Check WebCron preparation, registration state hashing, Scheduler configuration-change events, and explicit connection tests.
Lifecycle
- QCTNH reads System - Schedule Runner parameters and enables WebCron.
- If no WebCron key exists, it generates a random Joomla key and saves it.
- Registration sends the current exact native endpoint/key to QuantaCade over the authenticated service path.
- QCTNH stores a local SHA-256 hash of the registered key for drift detection.
- When Joomla Scheduler configuration is saved, the QCTNH system plugin triggers WebCron synchronization.
- If the current key hash no longer matches the registered hash, QCTNH does not treat the site as fully registered until synchronization succeeds.
- Worker wake-ups append the centrally stored key as Joomla’s
hashparameter.
Credential rotation
If exposure is suspected, rotate/regenerate the key in Joomla, then run Check WebCron/Test Connection as needed. Do not keep an old leaked key merely to avoid resynchronization.
Architecture context
Joomla WebCron Credential Synchronization Lifecycle belongs to the 2.0.3 native-WebCron architecture. QCTNH’s local component/plugin produces scheduler state and authenticated check-ins; the central service stores the validated endpoint/credential and schedules work; the worker calls Joomla WebCron; Joomla selects and runs the task.
This separation is useful when reading reference behavior because not every value is owned by the same layer. Task recurrence/locks belong to Joomla, wake-up timing belongs to the service, and identity/origin protection spans the local and central registration state.
Community Discussion
Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.