Token-based authentication (JWT) in IOT Protocols - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does JWT stand for in token-based authentication?

JWT stands for JSON Web Token. It is a compact, URL-safe token format used to securely transmit information between parties.

beginner

What are the three parts of a JWT?

A JWT has three parts separated by dots: Header, Payload, and Signature. The Header describes the token type and algorithm, the Payload contains claims or data, and the Signature verifies the token's integrity.

intermediate

How does a device use a JWT in IoT communication?

The device sends the JWT with its requests to prove its identity. The server checks the token's signature and validity before allowing access to resources.

intermediate

Why is the signature part important in a JWT?

The signature ensures the token was not changed after it was issued. It is created using a secret key or private key and helps the server trust the token.

beginner

What is a common use case for JWT in IoT devices?

JWTs are used to authenticate devices securely without sending passwords repeatedly. This helps devices connect to cloud services or APIs safely.

What part of a JWT contains the information about the user or device?

A Header

B Payload

C Signature

D Token type

The Payload part contains claims or data about the user or device.

Which of these ensures the JWT has not been tampered with?

A Payload

B Header

C Issuer

D Signature

The Signature verifies the token's integrity and prevents tampering.

In token-based authentication, what does the device send to the server?

A JWT

B Password

C Username only

D IP address

The device sends the JWT to prove its identity.

Which algorithm type is commonly specified in the JWT header?

A RSA or HMAC

B MD5

C AES

D SHA-256

JWT headers usually specify algorithms like RSA or HMAC for signing.

Why are JWTs useful in IoT devices?

A They replace hardware keys

B They store large files

C They allow secure, stateless authentication

D They encrypt all device data

JWTs enable secure, stateless authentication without needing to store session info on the server.

Explain how a JWT is structured and why each part is important.

Think about what information each part holds and how it helps secure communication.

Describe how token-based authentication with JWT improves security in IoT devices.

Consider how JWT helps devices prove who they are safely.

Practice

1. What is the main purpose of a JWT (JSON Web Token) in IoT device communication?

easy

A. To store large files securely on the device

B. To encrypt all data sent between devices

C. To prove the device's identity without sending passwords repeatedly

D. To replace the device's IP address

Solution

1. Step 1: Understand JWT role in authentication

   JWT tokens are used to prove identity securely without resending passwords each time.

2. Step 2: Compare options with JWT purpose

   Only To prove the device's identity without sending passwords repeatedly matches this purpose; others describe unrelated functions.

3. Final Answer:

   To prove the device's identity without sending passwords repeatedly -> Option C

4. Quick Check:

   JWT = Identity proof without password [OK]

Hint: JWTs prove identity without passwords [OK]

Common Mistakes:

• Thinking JWT encrypts all data
• Confusing JWT with file storage
• Assuming JWT replaces IP addresses

2. Which of the following is the correct structure of a JWT token?

easy

A. header.payload.signature

B. payload.header.signature

C. signature.payload.header

D. header.signature.payload

Solution

1. Step 1: Recall JWT token parts order

   A JWT consists of three parts separated by dots: header, payload, and signature in that order.

2. Step 2: Match options with correct order

   Only header.payload.signature shows header.payload.signature correctly.

3. Final Answer:

   header.payload.signature -> Option A

4. Quick Check:

   JWT format = header.payload.signature [OK]

Hint: JWT parts order: header, payload, signature [OK]

Common Mistakes:

• Mixing the order of parts
• Placing signature before payload
• Confusing payload and header positions

3. Given this JWT payload JSON: {"sub":"device123","exp":1700000000}, what does the "exp" field represent?

medium

A. The token's signature

B. The device's unique ID

C. The encryption algorithm used

D. The token's expiration time as a Unix timestamp

Solution

1. Step 1: Identify the meaning of 'exp' in JWT payload

   The 'exp' field stands for expiration time, given as a Unix timestamp.

2. Step 2: Match 'exp' meaning with options

   The token's expiration time as a Unix timestamp correctly states it is the token's expiration time; others are unrelated.

3. Final Answer:

   The token's expiration time as a Unix timestamp -> Option D

4. Quick Check:

   exp = expiration time [OK]

Hint: "exp" means token expiration time [OK]

Common Mistakes:

• Confusing 'exp' with device ID
• Thinking 'exp' is encryption info
• Mixing 'exp' with signature data

4. You receive this JWT token string: eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJkZXZpY2UxMjMiLCJleHAiOjE3MDAwMDAwMDB9. When verifying, you get an error about the signature. What is the most likely cause?

medium

A. The token is missing the expiration field

B. The token's signature does not match because the secret key used is incorrect

C. The header is not base64 encoded

D. The payload is missing the device ID

Solution

1. Step 1: Understand signature verification in JWT

   Signature errors usually happen when the secret key used to verify does not match the one used to sign.

2. Step 2: Check other options for signature error cause

   Missing payload fields or encoding issues cause different errors, not signature mismatch.

3. Final Answer:

   The token's signature does not match because the secret key used is incorrect -> Option B

4. Quick Check:

   Signature error = wrong secret key [OK]

Hint: Signature errors usually mean wrong secret key [OK]

Common Mistakes:

• Assuming missing fields cause signature errors
• Ignoring base64 encoding correctness
• Thinking expiration absence causes signature failure

5. You want to limit IoT device access by making JWT tokens expire after 10 minutes. Which approach correctly sets this expiration in the token payload?

hard

A. Set the "exp" field to the current Unix timestamp plus 600 seconds

B. Set the "iat" field to 600

C. Set the "exp" field to the current date string

D. Omit the "exp" field to allow unlimited token life

Solution

1. Step 1: Understand JWT expiration setting

   The 'exp' field must be a Unix timestamp indicating when the token expires, so add 600 seconds (10 minutes) to current time.

2. Step 2: Evaluate other options

   'iat' is issued-at time, not expiration; date string is invalid format; omitting 'exp' disables expiration.

3. Final Answer:

   Set the "exp" field to the current Unix timestamp plus 600 seconds -> Option A

4. Quick Check:

   Use 'exp' with timestamp + 600 seconds [OK]

Hint: Use 'exp' = now + 600 seconds for 10-minute expiry [OK]

Common Mistakes:

• Using 'iat' instead of 'exp' for expiration
• Setting 'exp' as a date string
• Leaving out 'exp' to limit token life