2.5.2.8 Create and Invoke a Pipeline — PSRP Client

Goal: To create and invoke a pipeline.

Context of use: This use case occurs when the WM user has to invoke a pipeline.

Actors

  • PSRP client: The primary actor that triggers this use case.

  • PSRP server: A supporting actor that responds to network requests that are initiated by the PSRP client.

  • Authentication services: A supporting actor that provides authentication services through NTLM, Kerberos, Basic, and Digest authentication to secure communications. It also provides authentication services that support the client-to-server communication. For an overview of the Authentication Services protocols, see [MS-AUTHSOD].

Stakeholders

  • WM user: A person or management application who has to access or change a set of system resources for a set of computers. The primary interest of the WM user is to create and invoke a pipeline.

Preconditions: The RunspacePool is in an opened state on the PSRP client role.

Main success scenario

  1. Trigger: A request from the WM user triggers this use case. The PSRP client sends a request to the server by using a wxf:Command message, as specified in [MS-PSRP] section 3.1.5.3.3, to create a pipeline.

  2. The PSRP server initializes the pipeline state to NotStarted and then processes and validates the message. Then it sends a success message if the validation is successful.

  3. The PSRP client sends a request to the server by using a wxf:Send message, as specified in [MS-PSRP] section 3.1.5.3.5, to invoke a pipeline.

  4. The PSRP server changes the pipeline state to Running and starts executing the pipeline.

Post condition

The PSRP client receives notification about the execution of the pipeline.

Extensions: If the communication channel cannot be established or becomes disconnected, it causes the protocol to tear down all related communications and update any necessary data structures to maintain the system state, as described in section 2.10.1.