-
Notifications
You must be signed in to change notification settings - Fork 10
Description
As a Resource Owner/Controller,
I want to easily, yet securely, change my Authorization Service(s), without losing my policies,
So that I am not bound to my initial choice, or the service provided by the pod host.
Preconditions:
What conditions must be in place or assumed before this use case can begin?
Trigger:
What (user or system) event or action initiates this use case?
Actors:
Describe the primary actor, and any other relevant actors involved in this use case
Distinction:
What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?
Scenario:
Describe an ideal or happy-case scenario where this use case would play out as intended.
Alternative case(s):
What alternative flows or variations should the system handle for this use case?
Error scenario:
What unexpected issues or errors might arise, and how should the system handle them?
Acceptance Criteria:
What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?
References:
List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.