Force tokens during install and begin to force tokenization

Created on 18 November 2024, 5 months ago

4.x branch will be forcing tokenized URLs.
During the install process we will now force a Maestro orchestrator token and a sitewide token.

1. Documentation to be updated
2. Tokenization in code to be forced during install and made mandatory for sitewide token.

📌 Task
Status

Active

Version

4.0

Component

Code

Created by

🇨🇦Canada _randy

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @_randy
    • _randy committed ef969163 on 4.x
      Issue #3488203: Force tokens during install and begin to force...
  • 🇨🇦Canada _randy

    I have also added an install hook and update hook only in the 4.x branch.

    Install hook will preset the 2 tokens for orchestrator and sitewide token. It is suggested that you configure those for your own purposes. They are mandatory.

    The update hook will update any open task with a token (If it doesn't already have one). If you are manually tracing and changing status of closed processes or tasks, you are responsible for setting tokens on those tasks which are now unarchived and not completed.

    Notifications to be updated next.

    • _randy committed 55145a02 on 4.x
      Issue #3488203: Force tokens during install and begin to force...
  • 🇨🇦Canada _randy

    Default notifications now use token instead of queueID.

Production build 0.71.5 2024