Orchestration of PAM actions

The sequence of module invocations per action.

• By default, modules are executed sequentially.

• Each module has its parameters and calling semantics.

  • Required, requisite, sufficient, optional.

• Execution proceeds until the end, or failure.

  • To better hide the source of a failure, module execution can either abort immediately or delay the failure upon executing the entire sequence.

• Applications can recover from failures.