Who is this article for?
CrashPlan for Enterprise, yes.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
This article applies to on-premises authority servers.
This article explains how to interpret and respond to the following alert.
The table below displays where the alert appears and where it can be configured.
|"Identity provider name does not support HTTP POST"||Delivered by email and to the Alerts Overview of the Code42 console|
|"SSO IDP doesn't support HTTP Post"||Settings > Notifications of the Code42 console|
This alert indicates a problem that could seriously affect your Code42 environment's security, result in data loss, or make the service unavailable.
This alert is triggered when your Code42 environment attempts to contact an SSO identity provider that does not support SAML 2.0 HTTP POST binding.
Users cannot sign in to your Code42 environment using SSO until this issue is resolved.
To resolve this alert, confirm that your identity provider supports SAML 2.0 HTTP POST binding.
Acknowledge the alert
An alert appears in the Code42 console's list of active alerts until someone dismisses it. To dismiss an alert:
- (Version 6.5 and later) Go to Active Alerts, select the alert, then go to the action menu and choose Dismiss.
- (Before version 6.5) Go to Alerts Overview, select the alert, then go to the action menu and choose Acknowledge.