Export (0) Print
Expand All

3.3.4.1.4 Delete Directory Object - Client Application

Goal: Delete a directory object from the Active Directory System.

Context of Use: An Administrator can perform maintenance on an Active Directory System by removing objects that are no longer needed by the Client Application. To achieve this, an Administrator launches the Client Application to interact with the Active Directory System. The Client Application establishes a connection to the Active Directory System. The Administrator performs a delete on an existing directory object.

Direct Actor: The direct actor is the Client Application.

Primary Actor: The primary actor is the Administrator that is requesting the delete on the directory object.

Supporting Actors: The supporting actor is Windows Authentication Services [MS-AUTHSO]. Windows Authentication Services are responsible for authenticating the Administrator's identity so that access control decisions can be made by the Active Directory System.

Stakeholders and Interests:

  • Developer: The Developer relies on the correct behavior of the Active Directory System so that the Client Application functions as expected.

  • Tester: The Tester needs to verify that the Client Application functions according to specification.

  • Application architect: The application architect designs the Client Application and determines how data is stored in the application NC.

Preconditions:

  • The Active Directory System MUST complete initialization as described in section 6.6. The system-wide preconditions specified in section 4.2 MUST be satisfied.

  • The direct actor MUST have access to a directory server to which it can establish a connection (if it is not already connected) and send the request.

  • The directory object to be deleted MUST exist in the Active Directory System.

Minimal Guarantees: If the main success scenario does not successfully finish, the Active Directory System guarantees that the directory is left unchanged.

Success Guarantee:

The directory object is transformed into some form of a deleted object. The specific form of the deleted object (Tombstone, Deleted-Object or Recycled-Object) depends on whether the Recycle Bin optional feature is enabled or not, as described in [MS-ADTS] sections 3.1.1.5.5.1.1, Tombstone Requirements, 3.1.1.5.5.1.2, Deleted-Object Requirements, and 3.1.1.5.5.1.3, Recycled-Object Requirements.

Trigger: The Administrator interacts with the Client Application and selects the directory object to delete and submits the deletion request to the Active Directory System.

Main Success Scenario:

  1. The Administrator launches the Client Application.

  2. The Client Application establishes a connection to a directory server and provides credentials supplied by the Administrator. Windows Authentication Services authenticates the Administrator using the supplied credentials ([MS-AUTHSO] section 4, Interactive Domain Logon Task).

  3. The Administrator provides the name of the directory object to delete to the Client Application.

  4. The Client Application sends a delete request to the directory server asking it to delete the specified directory object.

  5. The directory server validates that the Administrator has the necessary access-control rights to complete the operation ([MS-ADTS] section 5.1.3, Authorization).

  6. The directory server deletes the object as specified by the client and makes any additional modifications that are mandated by the server's processing rules and constraints; see [MS-ADTS] sections 3.1.1.5.1, General, and 3.1.1.5.5, Delete Operation.

  7. The directory server sends back a response to the Client Application indicating that the deletion was completed successfully.

Extensions:

  • If the Administrator has insufficient access-control rights to delete the directory object:

    1-4. Same as Main Success Scenario.

    5. If the Administrator does not have access-control rights to see the object that is to be deleted, the directory server sends a response back to the Client Application indicating that no such object exists. Otherwise, the directory server sends a response back to the Client Application indicating that it has insufficient access-control rights to delete the directory object.

  • If the Administrator attempted a delete on a non-leaf directory object:

    1-5. Same as Main Success Scenario.

    6. The directory server sends a response back to the Client Application indicating that it cannot delete a non-leaf object ([MS-ADTS] section 3.1.1.5.5.5, Constraints).

  • If the Administrator attempted a delete on a directory object that is owned by the system ([MS-ADTS] section 3.1.1.5.5.3, Protected Objects):

    1-5. Same as Main Success Scenario.

    The directory server sends a response back to the Client Application indicating that it will not perform the operation.

System Details: Additional architectural details of this use case are covered in section 6.1.9.

 
Show:
© 2014 Microsoft