Single Sign-On (SSO) in Cybersecurity - Time & Space Complexity

Time Complexity: Single Sign-On (SSO)

O(n)

Understanding Time Complexity

When using Single Sign-On (SSO), it's important to understand how the time to authenticate grows as more applications or users are involved.

We want to know how the system's work changes when more users or services use SSO.

Scenario Under Consideration

Analyze the time complexity of the following simplified SSO authentication flow.

function authenticateUser(user, services) {
  if (!validateUser(user)) {
    return false;
  }
  for (let service of services) {
    if (!checkAccess(user, service)) {
      return false;
    }
  }
  return true;
}

This code checks if a user is valid, then verifies access to each service in the list before granting SSO access.

Identify Repeating Operations

• Primary operation: Looping through each service to check access.
• How many times: Once for each service the user wants to access.

How Execution Grows With Input

As the number of services increases, the time to check access grows proportionally.

Input Size (n = number of services)	Approx. Operations
10	10 access checks
100	100 access checks
1000	1000 access checks

Pattern observation: The work grows in a straight line as more services are checked.

Final Time Complexity

Time Complexity: O(n)

This means the time to authenticate grows directly with the number of services checked.

Common Mistake

[X] Wrong: "SSO authentication time stays the same no matter how many services are involved."

[OK] Correct: Each service requires an access check, so more services mean more work and longer time.

Interview Connect

Understanding how authentication time grows with services helps you explain system performance clearly and shows you grasp real-world security challenges.

Self-Check

"What if the system cached access checks for services? How would that change the time complexity?"

Practice

1. What is the main benefit of Single Sign-On (SSO) for users?

easy

A. Require two-factor authentication for every login attempt

B. Use different passwords for every application to increase security

C. Log in once to access multiple applications without re-entering passwords

D. Automatically change passwords every day for all accounts

Solution

1. Step 1: Understand SSO purpose

   SSO allows users to log in once and access many apps without repeated logins.

2. Step 2: Compare options

   Only Log in once to access multiple applications without re-entering passwords describes this main benefit; others describe different security methods.

3. Final Answer:

   Log in once to access multiple applications without re-entering passwords -> Option C

4. Quick Check:

   SSO = Single login for many apps [OK]

Hint: SSO means one login for many apps [OK]

Common Mistakes:

• Confusing SSO with password rotation
• Thinking SSO requires multiple passwords
• Mixing SSO with two-factor authentication

2. Which of the following is the correct description of how SSO works?

easy

A. Users enter credentials separately for each app

B. Users authenticate once and receive a token to access other apps

C. Users must reset passwords before accessing each app

D. Users share passwords between apps manually

Solution

1. Step 1: Identify SSO mechanism

   SSO uses a single authentication that issues a token for other apps.

2. Step 2: Eliminate incorrect options

   Options B, C, and D describe separate logins or insecure practices, not SSO.

3. Final Answer:

   Users authenticate once and receive a token to access other apps -> Option B

4. Quick Check:

   SSO = One auth, token for others [OK]

Hint: SSO uses one token after one login [OK]

Common Mistakes:

• Thinking SSO requires multiple logins
• Confusing token with password
• Assuming password sharing is part of SSO

3. Consider this scenario: A user logs in via SSO and receives a session token valid for 1 hour. What happens if the user tries to access a second app after 2 hours without logging in again?

medium

A. Access is denied because the session token expired

B. Access is granted but with limited features

C. Access is granted because the user logged in once

D. Access is denied because the user must reset password

Solution

1. Step 1: Understand session token validity

   The token is valid for 1 hour, so after 2 hours it expires.

2. Step 2: Determine access after expiration

   Without a valid token, access is denied until re-authentication.

3. Final Answer:

   Access is denied because the session token expired -> Option A

4. Quick Check:

   Expired token = no access [OK]

Hint: Expired token means no access [OK]

Common Mistakes:

• Assuming one login lasts forever
• Confusing token expiration with password reset
• Thinking limited features are given after expiry

4. A company implements SSO but users report they are asked to log in again for each app. What is the most likely cause?

medium

A. SSO tokens are not shared properly between applications

B. Users forgot their passwords

C. The company uses different passwords for each app

D. Users have disabled cookies in their browsers

Solution

1. Step 1: Identify SSO failure reason

   If users must log in repeatedly, tokens are likely not shared or recognized.

2. Step 2: Evaluate other options

   Password issues or cookie settings may affect login but token sharing is key for SSO.

3. Final Answer:

   SSO tokens are not shared properly between applications -> Option A

4. Quick Check:

   Token sharing failure = repeated logins [OK]

Hint: SSO needs token sharing between apps [OK]

Common Mistakes:

• Blaming user passwords instead of token issues
• Ignoring browser cookie settings
• Assuming different passwords cause SSO failure

5. A company wants to improve security while using SSO. Which combination best balances ease of use and security?

hard

A. Use SSO without passwords but require manual approval for each app

B. Use SSO with weak passwords but frequent password changes

C. Use separate passwords for each app and no SSO

D. Use SSO with strong passwords and multi-factor authentication

Solution

1. Step 1: Identify security best practices with SSO

   Strong passwords and multi-factor authentication protect the single login well.

2. Step 2: Compare options for balance

   Use SSO with strong passwords and multi-factor authentication combines ease (SSO) and strong security; others reduce usability or weaken security.

3. Final Answer:

   Use SSO with strong passwords and multi-factor authentication -> Option D

4. Quick Check:

   Strong auth + SSO = secure and easy [OK]

Hint: Strong auth plus SSO improves security [OK]

Common Mistakes:

• Ignoring multi-factor authentication
• Thinking weak passwords are acceptable with SSO
• Believing manual approvals replace strong auth