Scoped Permission Exercise

Scoped Permission Exercise

A gateway is a device that passes local device traffic into another service path. Write one allowed request with the subject, action, resource, conditions, and decision owner. Then write a nearby request that must be refused. Choose the simplest rule structure that can express both cases without giving the controller a wider role.

Try the allowed request, a request for another floor, a door command, an expired identity, and a request during maintenance. Check that each decision records the rule and context it used. Remove the floor assignment and repeat the test to expose stale permission.

This exercise does not prove every user or fleet rule. The deeper sections compare owner-set, centrally set, role-based, attribute-based, and token-held permission models, then show where each one becomes hard to manage.

Back to the chapter