Propose new functionalities for Decidim software

Fingerprint

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: 0666c3f177653d213757094602e2eb7b628f34fffec14b4825726929a65d173f

Source: {"body":"Currently Decidim is somewhat \"locked\" to the OmniAuth strategies that it ships with as defined here:\r\nhttps://git.io/Je4p5\r\n\r\nTo add new methods, you will need to override the constant which is a bad convention.\r\n\r\nAnother thing is that with certain OmniAuth strategies, we need to have the control over the callback route and possibly also of the sign out route (in order to send a sign out request to the service in question). These are not straight forward to implement in Decidim right now.\r\n\r\nAs an example, you can take a look at the Suomi.fi module we've built which is a SAML2 based authentication method:\r\nhttps://github.com/mainio/decidim-module-suomifi\r\n\r\nHere is what we need to do to add the new OmniAuth strategy in the first place:\r\nhttps://git.io/Je4pF\r\n\r\nHere is what we need to do to take control of the callback and passthru routes:\r\nhttps://git.io/Je4pb\r\n\r\nHere is what we need to do to take control of the sign out flow:\r\nhttps://git.io/Je4pA\r\nhttps://git.io/Je4pp\r\n\r\nIf you spend few moments investigating those pieces of code, you will notice that it's quite a hack currently to implement these. It's even worse when we have to implement multiple methods that all need e.g. individual sign out flow controls.","title":"Better control of the OmniAuth authentication flows + adding new OmniAuth strategies"}

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. ×