All Collections
Teams and Organizations
SAML
Signature didn't verify. Contents have been tampered with or the wrong signature was used to verify.
Signature didn't verify. Contents have been tampered with or the wrong signature was used to verify.
Matt Houser avatar
Written by Matt Houser
Updated over a week ago

We have noticed that when using Skeddly SSO from some IdPs, some users may encounter the following error:

Signature didn't verify. Contents have been tampered with or the wrong signature was used to verify.

If you encounter this error, determine whether the user's name (first name, last name, and/or display name) includes any non-ASCII characters. These may include any of (but not limited to) the following: ä, ĉ, ç, é, ñ, or other non-Latin characters.

If this is the case, you can avoid the issue by excluding the user's name details from the SAML assertion (Skeddly does not require them).

Azure AD Resolution

In Azure AD, edit the "User Attributes & Claims" and delete any attributes related to the following:

  • display name

  • surname

  • first name

Did this answer your question?