Propose new features
Designing Decidim together
Better control of the authorization permission requirements for a component
List of Endorsements
Report inappropriate content
Is this content inappropriate?
We use cookies to ensure the basic functionalities of the website and to enhance your online experience. You can choose for each category to opt-in/out whenever you want.
These cookies are essential for the proper functioning of my website. Without these cookies, the website would not work properly.
These cookies allow the website to remember the choices you have made in the past
Analytics cookies are cookies that track how users navigate and interact with a website. The information collected is used to help the website owner improve the website.
These cookies collect information about how you use the website, which pages you visited and which links you clicked on.
Designing Decidim together
The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.
Value:
cf4ced197be25dc742714bae47aa5502d531d6459d7a883ed56545d7940e013e
Source:
{"body":{"en":"BACKGROUND\r\nCurrently Decidim allows to define required authorizations for a component and add specific rule requirements to the authorizations. The action authorizers can then be configured to check these requirements.\r\n\r\nPROBLEM\r\nWhen the above is configured for multiple authorizations, Decidim requires ALL of the authorizations to be valid as defined by:\r\nhttps://git.io/fjFaH\r\n\r\nThis causes a problem when we would only like to have one of the authorization to pass OR always require one specific authorization + one of the other configured authorizations.\r\n\r\nSOLUTION\r\nThere are few possibilities how to solve this but I think the most flexible solution would be to introduce programmatic authorization control flows which could be then selected in the permissions view of the component from a dropdown. There would always be only one authorization control flow which would apply to the component to check whether the user is authorized.\r\n\r\nBy default there could be two different flows:\r\n- Require all authorizations to pass\r\n- Require one of the authorizations to pass\r\n\r\nThen the developers could register their own flows to customize the functionality of these (e.g. one specific one required + one of the others).\r\n\r\nOther solution suggestions are welcome as well, this was just the first though.\r\n\r\nRight now, we are bypassing the problem using another combined authorization which does what is explained above. From the users perspective this is not ideal as they will see this \"extra\" authorization in the authorizations list and it may cause some confusion."},"title":{"en":"Better control of the authorization permission requirements for a component"}}
This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.
<script src="https://meta.decidim.org/processes/roadmap/f/122/proposals/14753/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/14753/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>
Is this content inappropriate?
You need to enable all cookies in order to see this content.
Change cookie settings
2 comments
Loading comments ...
Add your comment
Sign in with your account or sign up to add your comment.
Loading comments ...