Troubleshooting Suggestions

If you experience errors, while implementing Web Elements or SSO, referto these troubleshooting steps.

  • Clients should maintain a UAT site where they test all changes to the SSO and Web Elements before they move to production. This will allow us and them to determine fixes to issues created by software changes before those changes are made on production. In essence, the Production site should never contain newer software than the UAT site.
  • If the server error "No Identity provider could be found for this request"  appears when accessing the Widgetized portal URL, the system cannot determine an Identity provider:
    • One common issue for this is a typo in the Service Configuration or Service Configuration Property for the SAML service. Request that Cobalt staff examine the service configuration if you observe this error.
    • Confirm that you a SAML Service Configuration has actually been created. It is possible for user to successfully perform configurations steps out of order, making it possible to forget to create a Service Config.
  • If the Object Moved to Here message appears persistently when accessing the Widget Site URL:
    • Competing Service Configurations. If this error does not disappear after creating a Widget Site configuration, confirm that there are no Active, Enabled Service Configurations that you didn't intend on using and that don't serve one of their current integrations
    • That the Widget Service Config is not associated to both the Integration Settings and SSO Settings
  • If the Cobalt IDP Metadata throws an error:
    • The IDP Service Conifg maybe missing the Client ID and Client Password Service Config Properties
  • If the server error "Failed to verify signature on HTTP redirect message" appears, this indicates that the widgetized portal cannot be redirected to. Confirm that the SAML service configuration is correctly configured, with all of the necessary properties and values, then restart the site and app pool for the Widgetized portal in IIS on the portal's server
  • If you receive a 500 Internal Server Error when attempting to access the widgetized portal, navigate to the associations portal mirror(s) to confirm that the site and app pool is active in IIS (Internet Information Services). If so (and the error is still occurring) navigate to the portal site, then double-click Application Settings in the Home window. If you receive an error, the error will indicate a portal file that is causing the error.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk