Add example of algorithm_exceptions

main/docs/authenticate/protocols/saml/saml-sso-integrations/sign-and-encrypt-saml-requests.mdx

@@ -113,7 +113,9 @@ Download the certificate in the format requested by the IdP.
 By default, Auth0 automatically supports the algorithms listed in the latest [Algorithm Profile](/docs/authenticate/protocols/saml/saml-sso-integrations/algorithm-profiles) for decrypting SAML assertions. 
 
 <Callout icon="file-lines" color="#0EA5E9" iconType="regular">
-If the assertion is encrypted with an algorithm not in the list, then the assertion will be rejected by Auth0.
+- If the assertion is encrypted with an algorithm **not** in the list, then the assertion will be rejected by Auth0.
+
+- If your IdP does not support an algorithm in the list, you can use the `algorithm_exceptions` parameter to override the security profile. Auth0 recommends to use the latest [Algorithm Profile](/docs/authenticate/protocols/saml/saml-sso-integrations/algorithm-profiles) for decrypting SAML assertions. 
 </Callout>
 
 To specify a different profile or use an unlisted algorithm, you need to update the connection using the [Update a Connection](https://auth0.com/docs/api/management/v2/connections/patch-connections-by-id) endpoint and change the `assertion_decryption_settings` property as shown in the payload example below.
@@ -129,7 +131,12 @@ Payload:
     [...], // all the other connection options
     "assertion_decryption_settings": {
       "algorithm_profile": "v2026-1",
-      "algorithm_exceptions": []
+      "algorithm_exceptions": [
+        // You can override the security profile to use a less secure algorithm, for example:
+		// "http://www.w3.org/2001/04/xmlenc#aes128-cbc",
+		// "http://www.w3.org/2001/04/xmlenc#aes256-cbc",
+		// "http://www.w3.org/2001/04/xmlenc#tripledes-cbc"
+	  ]
     }
   }
 }