OAuth 2.0 and OpenID Connect in Cybersecurity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is OAuth 2.0?

OAuth 2.0 is a protocol that allows a user to grant limited access to their resources on one site to another site, without sharing their password. It is mainly used for authorization.

beginner

What is OpenID Connect (OIDC)?

OpenID Connect is an identity layer built on top of OAuth 2.0. It allows clients to verify the identity of the user and obtain basic profile information in a secure way.

intermediate

What is the main difference between OAuth 2.0 and OpenID Connect?

OAuth 2.0 is for authorization (granting access to resources), while OpenID Connect adds authentication (verifying who the user is) on top of OAuth 2.0.

beginner

What is an access token in OAuth 2.0?

An access token is a string issued by the authorization server that allows the client to access protected resources on behalf of the user for a limited time.

intermediate

What is an ID token in OpenID Connect?

An ID token is a JSON Web Token (JWT) issued by the OpenID provider that contains information about the user’s identity, such as their unique ID and authentication time.

Which protocol is primarily used for user authentication?

A FTP

B OAuth 2.0

C OpenID Connect

D HTTP

OpenID Connect is designed for authentication, allowing verification of user identity.

What does OAuth 2.0 allow a user to do?

A Verify their identity

B Encrypt their data end-to-end

C Create a new user account

D Grant limited access to their resources without sharing passwords

OAuth 2.0 lets users authorize third parties to access their resources without sharing passwords.

What type of token contains user identity information in OpenID Connect?

A ID token

B Refresh token

C Access token

D Session token

The ID token contains user identity details in OpenID Connect.

Which of these is NOT a role in OAuth 2.0?

A Resource Owner

B Identity Provider

C Authorization Server

D Resource Server

Identity Provider is a role in OpenID Connect, not OAuth 2.0 specifically.

What does the access token allow a client to do?

A Access protected resources

B Change user passwords

C Authenticate the user

D Create new users

Access tokens allow clients to access protected resources on behalf of the user.

Explain how OAuth 2.0 and OpenID Connect work together to provide secure access and identity verification.

Think about how one protocol controls access and the other confirms who the user is.

Describe the purpose of access tokens and ID tokens in OAuth 2.0 and OpenID Connect.

Consider what each token allows the client or server to do.

Practice

1. What is the main purpose of OAuth 2.0 in online applications?

easy

A. To allow apps to access user data without sharing passwords

B. To encrypt all user data during transmission

C. To replace passwords with biometric authentication

D. To store user passwords securely on servers

Solution

1. Step 1: Understand OAuth 2.0's role

   OAuth 2.0 is designed to let apps get permission to access user data without needing the user's password.

2. Step 2: Compare options to OAuth 2.0's purpose

   Storing passwords securely, encrypting data during transmission, and replacing passwords with biometrics describe other security features but not OAuth 2.0's main function.

3. Final Answer:

   To allow apps to access user data without sharing passwords -> Option A

4. Quick Check:

   OAuth 2.0 = Access without password [OK]

Hint: OAuth 2.0 = permission without password sharing [OK]

Common Mistakes:

• Confusing OAuth 2.0 with encryption protocols
• Thinking OAuth 2.0 replaces passwords
• Assuming OAuth 2.0 stores passwords

2. Which of the following is a correct OAuth 2.0 grant type?

easy

A. Authorization Code

B. Password Encryption

C. Token Hashing

D. User Authentication

Solution

1. Step 1: Identify OAuth 2.0 grant types

   OAuth 2.0 defines several grant types, including Authorization Code, Implicit, Client Credentials, and Resource Owner Password Credentials.

2. Step 2: Match options to known grant types

   Only 'Authorization Code' is a valid OAuth 2.0 grant type; others are incorrect terms.

3. Final Answer:

   Authorization Code -> Option A

4. Quick Check:

   Grant type = Authorization Code [OK]

Hint: Grant types include Authorization Code, not encryption terms [OK]

Common Mistakes:

• Confusing grant types with encryption methods
• Selecting made-up OAuth terms
• Mixing authentication with grant types

3. Given this OAuth 2.0 flow snippet:

1. User clicks login
2. App redirects to Authorization Server
3. User grants permission
4. Authorization Server sends code to App
5. App exchanges code for access token

What is the purpose of step 5?

medium

A. To get the user's password

B. To obtain an access token for API calls

C. To verify the user's identity directly

D. To log the user out of the app

Solution

1. Step 1: Understand step 5 in OAuth 2.0 flow

   Step 5 is where the app exchanges the authorization code for an access token from the authorization server.

2. Step 2: Identify the purpose of the access token

   The access token allows the app to make authorized API calls on behalf of the user without needing their password.

3. Final Answer:

   To obtain an access token for API calls -> Option B

4. Quick Check:

   Step 5 = Get access token [OK]

Hint: Code exchanged for access token to call APIs [OK]

Common Mistakes:

• Thinking step 5 gets the password
• Confusing access token with identity verification
• Assuming step 5 logs out the user

4. A developer uses OpenID Connect but forgets to validate the ID token signature. What is the main risk?

medium

A. User passwords will be exposed

B. The app will crash immediately

C. The app might accept fake user identities

D. The access token will expire too soon

Solution

1. Step 1: Understand ID token validation

   Validating the ID token signature ensures the token is from a trusted source and not tampered with.

2. Step 2: Identify risk of skipping validation

   If validation is skipped, attackers could send fake tokens, letting unauthorized users impersonate others.

3. Final Answer:

   The app might accept fake user identities -> Option C

4. Quick Check:

   ID token validation prevents fake identities [OK]

Hint: Always validate ID token signature to trust identity [OK]

Common Mistakes:

• Assuming app crashes without validation
• Confusing token validation with password exposure
• Thinking token expiration is affected

5. An app uses OAuth 2.0 with OpenID Connect to authenticate users. It wants to get the user's email and profile info securely. Which token should the app request and verify?

hard

A. Refresh token only

B. ID token only

C. Access token only

D. Both access token and ID token

Solution

1. Step 1: Understand token roles in OpenID Connect

   The ID token proves the user's identity and contains profile info. The access token allows access to user data APIs.

2. Step 2: Determine which tokens to use for email and profile

   The app should verify the ID token for identity and use the access token to request additional user info securely.

3. Final Answer:

   Both access token and ID token -> Option D

4. Quick Check:

   ID token + access token = secure user info [OK]

Hint: Use ID token for identity, access token for data [OK]

Common Mistakes:

• Using only access token and ignoring ID token
• Using only ID token without access token
• Confusing refresh token with identity info