🐛 Allow creating tokens with CRON scope #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Base information
Symptom (bug) / Objective (enhancement)
Unable to create a token (personal or application) with
CRON
scope needed to run/webservices/cron.php
; theCRON
option is missing in the UI.This means that background tasks at
/webservices/cron.php
cannot be launched with token authentication.Reproduction procedure (bug)
CRON
scope is not listed/webservices/cron.php
Cause (bug)
Option simply missing from UI, but the
CRON
scope is handled in the code.Proposed solution (bug and enhancement)
Add option to UI in order to be able to add
CRON
scope to token.This PR adds the new value for the scope in the datamodel.
Other file modified are simply dictionary entries related.
Checklist before requesting a review
Checklist of things to do before PR is ready to merge
This PR contains also dictionary entries (made in the same way as previous ones) for the new
CRON
token scope.