For Security Compliance purposes - Huge companies have security requirements, such as the need to use encryption and signing certificates that are trusted by 3rd Party Root Authorities, in setting-up Single Sign-on, to encrypt and protect SAML assertions. Enabling the field to change the Encryption Certificate used in encryption will allow Monday.com to comply with these requirements, especially with the default certificate provided by Monday.com being self-signed, and is not trusted by a 3rd party Root Authority. This is akin to setting up a “Bring-your-own-Certificate” setup.
Since this is disabled by default, we are struggling to get compliance approval from our Security Architecture team, and have to go through an exception process just to get it officially approved.
