Flowchart 4: How owner authority is checked

Flowchart 4 shows the process for checking owner authority. The name of the owner profile and the owner's authority to an object are stored with the object.

Several possibilities exist for using the owner's authority to access an object:
  • The user profile owns the object.
  • The user profile owns the authorization list.
  • The user's group profile owns the object.
  • The user's group profile owns the authorization list.
  • Adopted authority is used, and the program owner owns the object.
  • Adopted authority is used, and the program owner owns the authorization list.
Figure 1. Flowchart 4: Owner authority checking
: Owner authority checking

Description of Flowchart 4: Owner authority checking

  1. The system determines if the user profile owns the object being checked. If the user profile does own the object, then it moves to Step 2. If the user profile does not own the object, then the system returns to the calling flowchart with no authority found.
  2. If the user profile does own the object, the system then determines if the owner has authority to the object. If the owner has authority to the object, then the authority check proceeds to Step 3. If the system determines that the owner does not have authority to the object, then the system returns to the calling flowchart with no authority found.
  3. If the owner does have authority to the object, then the system determines whether this authority is sufficient to access to object. If the authority is sufficient, then the owner is authorized to the object. If it is not sufficient, then the system returns to the calling flowchart with insufficient authority found.