Review authorization for a saved conversation route
An identifier is a lookup key rather than permission. Checking only that a user is signed in does not protect another user’s records.
Start here
This example uses the sample details below. Replace them with your own facts before applying the instructions.
- User A and User B have separate account histories.
Start with the facts
User A and User B have separate account histories. Keep a small reproducible example and the expected behavior. Remove secrets from the code or error message before requesting help.
Spot the problem
The wording or action to avoid is: “Allow access whenever the caller knows a conversation identifier.” An identifier is a lookup key rather than permission. Checking only that a user is signed in does not protect another user’s records.
Make the correction
Authorize the requested conversation against the authenticated account before returning or changing its contents.
Check before using the result
Create two test accounts and verify that neither can read, rename or delete the other account’s conversation.
Worked example and reusable input
Use the stated inputs to reproduce checked local outputs. Replace sample facts when applying a brief to your own work.
TASK Review authorization for a saved conversation route SAMPLE INPUT — replace with your actual facts User A and User B have separate account histories. AVOID Allow access whenever the caller knows a conversation identifier. CORRECTED APPROACH Authorize the requested conversation against the authenticated account before returning or changing its contents. ACCEPTANCE CHECK Create two test accounts and verify that neither can read, rename or delete the other account’s conversation.
Key takeaways
- An identifier is a lookup key rather than permission. Checking only that a user is signed in does not protect another user’s records.
- Create two test accounts and verify that neither can read, rename or delete the other account’s conversation.