| Excerpt | ||
|---|---|---|
| ||
Allows a user to construct a new activation key for a person and invalidates any currently existing one. |
Actors
- User
- Database
- OpenRegistry
...
- PRE1: User is authenticated and authorized.
- PRE2: Calculated Person has been created and chosen.
- PRE3: There are currently no other valid activation keys for the Calculated Person.
...
- 0 or 1 activation keys already in existence.
- PRE4: Validity Length for Activation Keys is configured outside of use case (start and end validity).
Flow
- If there is already a valid activation key, the key is deleted.
- An activation key is randomly generated and associated with the calculated person.
...
- Key is available to user who asked for initiated key creation.
Business Rules
- BR1: Activation Keys are valid for one month, unless invalidatedas defined in PRE4.
- BR2: Activation Keys are of the following format: 8 10 characters in length, consisting of characters [A-Za-z0-9]abcdefghijkmnopqrstuvwxyzABCDEFGHJKLMNPQRSTUVWXYZ2345679]
- BR3: Activation Keys cannot be changed. They can only be removed per the Delete Activation Key Use Case or expired naturally.
- BR4: An activation key is generated when a Calculated Person is first created. This activation key is generated with a maximum date range of 10 days which is the maximum length of time a key of this size should exist. Subsequent calls to Generate Activation Key can provide their own date range.