Loading
Slack 관련 문의처가 Salesforce Help로 통합 및 변경됩니다.더 많이 읽기

Slack Proactive Monitoring Alert: SSO Login Failures

게시 일자: Nov 10, 2026
상세 설명

This alert monitors SSO and SAML authentication failures for your organization using rate-of-change detection. It fires when failures in the current 30-minute window exceed both an absolute minimum and a multiple of the previous 24-hour average, or when the recorded reason indicates your SSO configuration could not be found at all. It is scoped to the failure reasons an administrator can act on, rather than to individual sign-in problems such as a mistyped password.

SSO failures mean users cannot sign in. Unlike a mistyped password, sustained SSO failures almost always indicate a configuration problem — an expired certificate, changed metadata, a wrong issuer, or an attribute mapping error — that an administrator can correct once they know about it. Without this alert, the breakage is usually discovered only when users report being locked out.

솔루션

1. Check your SAML/SSO configuration

Your settings are at:

  • Enterprise Grid: Organization settings → Security → SSO Settings
  • Single workspace: Admin → Workspace settings → Security → SSO & authentication

The quickest way to see what is actually failing is Test Configuration on that page. It performs a real sign-in round trip to your identity provider and returns the specific error encountered, which is the only place a precise SAML error is shown directly to an administrator — Slack's access logs record successful sign-ins rather than failed ones.

Then check each value Slack holds:

  • Identity provider metadata — the SAML 2.0 endpoint URL and the identity provider issuer must match what your provider is currently publishing. These are the values most often changed during a provider upgrade or migration.
  • Signing certificate expiry — check this in your identity provider, not in Slack. Slack validates the certificate you paste in but does not display its expiry date in SSO settings. Slack does send a Slackbot message to Workspace and Org Owners roughly 30 days before a SAML certificate expires; if that notice was missed or suppressed, the certificate may already have lapsed. When rotating a certificate, the new one has to be in place on both sides.
  • Issuer / entity ID — Slack holds both an identity provider issuer and a service provider issuer, and both must agree with your provider's configuration. A change on either side breaks sign-in for everyone.
  • Attribute mapping — this is configured entirely in your identity provider; Slack has no setting for it. If your Slack configuration is unchanged and Test Configuration still fails, the change is on the provider side.

Two things to know before you save anything. Saving any modified SAML field immediately re-authenticates you through your identity provider, so an incorrect value can sign you out of the page you are working on — keep a second Owner session available. And deleting an SSO configuration signs out everyone currently authenticated through that identity provider.

2. Review the most common failure reason in your case

Your case names the failure reason recorded most often during the window, which narrows the list above considerably.

If it is a configuration-not-found error, the failure is happening before your identity provider is ever contacted — Slack could not locate an active SSO configuration to send the request to. Confirm on the settings page above that your configuration is still present, active, and correctly saved.

3. If the configuration looks correct, contact Slack support referencing this alert

Reply to your case quoting the failure reason from the alert and noting whether Test Configuration passes. That pairing is normally enough for us to identify the cause quickly.

If no Owner is able to sign in at all, say so in your reply. Workspace Owners and Org Owners can normally sign in with an email address and password rather than SSO, which is how you would reach your settings during an outage — but if your organization has configured SSO to be required for Owners as well, that path is closed and we will need to help you regain access.

4. Note that this count is a lower bound

Slack can only count failures it observes. If your identity provider displays its own error page rather than returning the user to Slack, Slack never sees that failure. Treat the figure in your case as "at least this many," and expect that the number of affected users may be higher.

Knowledge 기사 번호

005462487

 
로드 중
Salesforce Help | Article