# Incorrect signingCert example in SAML Protocol Settings leading to login errors

**URL:** <https://community.auth0.com/t/incorrect-signingcert-example-in-saml-protocol-settings-leading-to-login-errors/196307>\
**Category:** Product Feedback\
**Tags:** idp, sp-initiated, saml2, auth0\
**Created:** [January 15, 2026, 2:26pm UTC](https://community.auth0.com/t/incorrect-signingcert-example-in-saml-protocol-settings-leading-to-login-errors/196307 "2026-01-15T14:26:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![giacomo.baso](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/giacomo.baso/32/78094_2.png) [@giacomo.baso](https://community.auth0.com/u/giacomo.baso)\
**Post date:** [January 15, 2026, 2:26pm UTC](https://community.auth0.com/t/incorrect-signingcert-example-in-saml-protocol-settings-leading-to-login-errors/196307/1 "2026-01-15T14:26:29Z")

</div>

**Feature:** Auth0 addon for SAML2 Web App suggests incorrect value for signingCert setting.

**Description:** In the addon settings, the description for signingCert states:

> Optionally indicates the public key certificate used to validate SAML requests. If set, SAML requests will be required to be signed. A sample value would be "-----BEGIN PUBLIC KEY----- MIGf…bpP/t3 +JGNGIRMj1hF1rnb6QIDAQAB -----END PUBLIC KEY----- ".

This is incorrect for two reasons:

- It suggests a PKCS#8 public key
- It suggests to replace line breaks with spaces

Configuring the addon as indicated leads to a login error with message: `invalid_request: error:1E08010C:DECODER routines::unsupported`

The only correct configuration is:

- Use a X.509 certificate instead of PKCS#8 public key
- Replace line breaks with `\n`

This is also indicated in the docs ( [Sign and Encrypt SAML Requests - Auth0 Docs](https://auth0.com/docs/authenticate/protocols/saml/saml-sso-integrations/sign-and-encrypt-saml-requests#receive-signed-saml-authentication-requests) ):

```json
{
  [...], // other settings
  "signingCert": "-----BEGIN CERTIFICATE-----\nMIIC8jCCAdqgAwIBAgIJObB6jmhG0QIEMA0GCSqGSIb3DQEBBQUAMCAxHjAcBgNV\n[..all the other lines..]-----END CERTIFICATE-----\n"
}

```

**Use-case:** Web application using Auth0 as SAML2 Identity Provider.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [February 27, 2026, 7:12pm UTC](https://community.auth0.com/t/incorrect-signingcert-example-in-saml-protocol-settings-leading-to-login-errors/196307/2 "2026-02-27T19:12:43Z")

</div>

Hi there!

Thank you for creating this feedback card and bringing this issue to our attention. Indeed, it appears to be quite an oversight.

Thanks,  
Nik
