Skip to content
CodeKruPro

C3 · Test access control and defend a release

32/32

06 · Independent projects

Recommended first: C2 · Independently test a saved customer lifecycle

Your goal: C3 · Test access control and defend a release

Read the lesson, then answer the questions. You do not need to write code.

Start here: sign in, then answer the questions.

Jump to practice

What you will learn

Your final project combines working authentication, known real records, authorization probes and a release recommendation. Write your plan first, then execute without a request guide. You may consult the earlier lessons and API reference.

Your goals

  • Execute positive controls and foreign-record probes independently.
  • Distinguish verified access protection from an unsupported release claim.

Before you start

Read the previous lesson first if you have not already. This course does not require programming.

Practice setup

These requests use the public TestKru teaching API. No workspace is needed unless a step says so. Leave the body empty for GET, HEAD and OPTIONS. Example people and emails are fictional. Changes to /api/users are simulated and are not saved.

Supplied training evidence / contract

Release brief REL67: isolation between customer A and B is mandatory. The only evidence supplied initially is successful login. No checkout, payment or refresh-rotation test has been executed. After your live ownership checks, recommend release only for the tested customer access slice, or hold if any required access check fails. Do not certify untested features.

Follow these steps

  1. Create this project’s workspace. Log in separately as B and A, keeping their tokens distinct. Read each list to obtain real owned record ids. Plan the own-record controls, denied read/write, and unchanged-state comparison.
  2. Read B’s specific record as B for before evidence. Read A’s different record as A for own evidence. Using A’s token, attempt GET and a valid name-only PATCH on B’s same id. Select all four named responses.
  3. Read B’s same record again as B and select the final comparison. Compare id, name, email, age, city and owner with before. Use the contract, not a guess, to decide whether A was allowed access.
  4. Record the denied-read status and reason, then choose the scope supported by these checks. Submit without resetting; stored B data is also checked.
  5. Keep a portfolio on your computer: clean collection from sharing, case plan, reproducible finding or contract question, before/after evidence, release recommendation and one automation-ready case. Use the rubric to assess writing quality; automatic checks do not certify your entire portfolio.

Investigate before concluding

First record the actual result for each case. Compare the body, headers and later state with the stated contract. Keep an observation separate from a prediction; use the model answer only after making your own attempt.

What to keep as evidence

  • Working tokens and real different owned ids support the probes.
  • Both denied operations and final read-back preserve B’s stored data.
  • The release recommendation names tested and untested scope.
References for this lesson

Finish this assignment

Answer from the transcript on this page. Click Submit Answers. Your score is the percentage of checks that passed. A saved 100/100 means every check passed. Continue opens the next lesson you can submit.

If something goes wrong
  • Change one part of the request at a time. If a check needs attention, read the note under it and compare it with the response you selected.
Self-review and independent variation
  • Working tokens and real different owned ids support the probes.
  • Both denied operations and final read-back preserve B’s stored data.
  • The release recommendation names tested and untested scope.

Repeat against a new workspace and different seeded ids; decide which rules and conclusions remain the same.

Automatic checks verify the requests and answers configured for this lesson. The self-review is for your own reasoning. A score is not a certificate.

Open API reference

Practise and save your evidence

The lesson is public. Sign in to send requests and save progress. You will return to this lesson.

Sign in to practiseCreate an account