Error Code Description
No signature was found in the SAML Response or Assertion.
Solution
It is required by the SAML 2.0 standard that either the response or assertion is signed. Please enable the same in your IDP.
Follow the steps below to resolve the error for the IdPs listed:
- Okta as IdP
- KeyCloak as IdP
Configuration steps for Okta as IdP:
Follow the steps below to resolve the ERROR WPSAMLERR003 for Okta:
- Once you are in the Okta Admin Dashboard, navigate to the Applications tab and select the application that you have created.
- Select the General tab and scroll down to the SAML Settings, and click on Edit.
- Click on Next button.
- Click on the Show Advanced Settings.
- For the fields Response and Assertion Signature, the dropdown option would be selected as Unsigned by default.
- For the Response or Assertion Signature field, select Signed as value from the dropdown. [ You can also enable both dropdown as signed ]
- Scroll down and click on Next button.
- Click on Finish button.
- Finally, In the WordPress SAML SSO plugin, go to the Service Provider Setup tab of the plugin.
- Click on Test Configuration to check if the ERROR WPSAMLERR003 for Okta has been resolved. If the error is fixed, the test is successful.
Configuration steps for KeyCloak as IdP:
Follow the steps below to resolve the ERROR WPSAMLERR003 for KeyCloak:
- Once you are in the Keycloak Admin console, click on Clients tab from the left menu and then click on the client/application which you have created.
- In the Settings tab only go to the Signature and Encryption section.
- As per the SAML 2.0 standard, either the Sign Documents or Sign Assertion must be signed. Please enable either one or both.
- Finally, In the WordPress SAML SSO plugin, go to the Service Provider Setup tab of the plugin.
- Click on Test Configuration to check if the ERROR WPSAMLERR003 for KeyCloak has been resolved. If the error is fixed, the test is successful.
Feel free to reach us at samlsupport@xecurify.com
