This is a big bug. I never saw it triggering because this never happens on Archipelago's that are upgraded from previous RC3 versions and was added BY ME on the last release. We have a UUID filling autocomplete for Metadata Display entities that allows to avoid breaking references when updating or reingesting Metadata Displays when preserving the UUID.
But Autocompletes use a special Key Value collection to keep track of settings and that is used in the permissions mechanism to check if the call is coming from a valid caller. FAIL, with this not being right the autocompletes will die with a 403 (Permission denied)
This is going to be a backwards fix on RC3 with a composer.lock update on archipelago-deployment and archipelago-deployment-live
@patdunlavey @aksm @alliomeria we will have to patch a few archipelagos and a Slack forum announcement with the composer command.
DiegoPino
commented
2 years ago
What?
This is a big bug. I never saw it triggering because this never happens on Archipelago's that are upgraded from previous RC3 versions and was added BY ME on the last release. We have a UUID filling autocomplete for Metadata Display entities that allows to avoid breaking references when updating or reingesting Metadata Displays when preserving the UUID.
But Autocompletes use a special Key Value collection to keep track of settings and that is used in the permissions mechanism to check if the call is coming from a valid caller. FAIL, with this not being right the autocompletes will die with a 403 (Permission denied)
This is going to be a backwards fix on RC3 with a composer.lock update on archipelago-deployment and archipelago-deployment-live
@patdunlavey @aksm @alliomeria we will have to patch a few archipelagos and a Slack forum announcement with the composer command.