Fix for the resetting of the Allow URI Access flag when server is started #3160
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.
Identify the Bug or Feature request
Fixes #3159
Description of the Change
The constructor to create a new token based on an existing token was not copying the All URI Access flag so it was defaulting to false. (Starting a new server copies zones/tokens from existing ones). This was causing the value of this flag to be lost when the server started.
Possible Drawbacks
None that I can think of
Documentation Notes
N/A Fixes a bug that was causing things to not work way people expected/was documented.
Release Notes
Fix for bug where Allow URI Access was being reset on server start.
This change is