Fix don't require inactive authorization handlers#8122
Fix don't require inactive authorization handlers#8122leio10 merged 5 commits intodecidim:developfrom
Conversation
leio10
left a comment
There was a problem hiding this comment.
LGTM, but I'd like @decidim/product to review this before merging it, as it's "subtle" behavior change.
Currently, the list of available authorization handlers managed through the system part is the list of authorizations that can be used for setting permissions. Disabling an authorization handler doesn't affect the components that are already configured.
With this PR, disabling an authorization handler will automatically stop using it everywhere.
I can think reasons for using both approaches, but I agree with @lahdeero that this new approach seems to be more intuitive.
I've discussed it with @carolromero and we both agree that in this case what we would expect is to NOT have the disabled authorization. Go ahead with merging the PR, please. Thanks! |
|
Please @lahdeero, can you backport this PR to 0.24? Thanks! |
* develop: (32 commits) Remove obsolete rake webpack task (#8237) Active storage migrations service (#7902) Fix content type delegation to blank attachments (#8230) Evote bug fixing (#8220) Fix the proposal data migration for proposals without authors or organization (#8015) Bump addressable version because security issues (#8229) Online meetings iframe visibility with time (#8097) Meetings iframe and iframe URL (#8096) Remove flaky test on meetings (#8226) Fix broken tests after problematic PRs (#8224) Apply permissions system to comments (#8035) Set current_component as commentable when commentable is a participatory space (#8189) Fix don't require inactive authorization handlers (#8122) Improve metrics calculations performance (#8215) Fix performance issue in notification settings page (#8155) Active storage migration (#7598) Update manual installation guide in documentation (#8217) Load JS configuration in elections focus mode layout (#8213) Fix user activity pagination when there are hidden items (#8202) Make it possible to define SCSS settings overrides from modules (#8198) ...
🎩 What? Why?
Currently when we change "Available authorizations" from system admin panel, it doesn't affect to component's permissions. So for example if we edit permissions from component, enable some authorization and after that we disable it from system admin, component still requires it.
Testing
📋 Checklist
🚨 Please review the guidelines for contributing to this repository.
docs/.📷 Screenshots