SSO (Single Sign-On)

SSO (single sign-on) lets a user authenticate once with a trusted identity provider and then access multiple applications without logging in again. The apps rely on the identity provider's signed assertion instead of managing their own passwords.

Why it matters

For organizations, SSO centralizes password policy, MFA enforcement and account removal. When an employee leaves, disabling one account cuts access everywhere. For users it means fewer passwords and fewer phishing opportunities. The trade-off is concentration: the identity provider becomes a critical dependency and a high-value target.

Example

At work you log in to the company portal with MFA, then open email, the ticket system and the HR tool without being asked for credentials again. Behind the scenes they use SAML or OpenID Connect to trust the provider.

Common mistakes

• Treating SSO as a replacement for MFA instead of protecting the identity provider with it.
• Forgetting to plan for an identity provider outage, which locks everyone out.
• Leaving local fallback passwords active in apps after enabling SSO.

Related

• SAML
• OAuth
• MFA
• Least privilege

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.