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, there are 2 known possible issues that could be happening.
Possible Issue 1
The most likely issue is that the Metadata from your IdP that was uploaded to Skeddly does not match the IdP that you're actually using. This could happen if you're testing Single Sign-on with one IdP and are switching over to your production IdP.
If this is the case, you can resolve this issue by doing the following:
Download the Metadata XML file from your IdP (Okta, Azure AD, etc.) Even if you've downloaded it previously, re-download it to ensure you're working with the correct file.
Upload the Metadata XML file to Skeddly. Either create a new Identity Provider in Skeddly with your new Metadata XML file, or update your existing Identity Provider in Skeddly with your new Metadata XML file.
Possible Issue 2
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
