{
  "context": "Evaluates how well the solution uses ldap3 to perform directory searches with explicit scope selection, alias dereference handling, and paged retrieval. The focus is entirely on correct application of ldap3 search controls and helpers rather than general code structure. Points reflect correct wiring of ldap3 primitives that expose search scopes, alias behavior, and paging cookies.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Scope constants",
      "description": "Maps the spec's scope strings to ldap3's search scope constants (BASE, LEVEL/ONELEVEL, SUBTREE) and passes them into Connection.search instead of manual filtering.",
      "max_score": 20
    },
    {
      "name": "Alias control",
      "description": "Configures dereference behavior by supplying ldap3 alias constants (e.g., DEREF_NEVER vs DEREF_ALWAYS) to Connection.search so alias resolution matches the requested mode.",
      "max_score": 20
    },
    {
      "name": "Scoped search",
      "description": "Issues ldap3 Connection.search calls with the provided base DN, filter, and attribute list, ensuring the chosen scope drives which entries are returned (base, one-level, or subtree) without extra client-side filtering.",
      "max_score": 20
    },
    {
      "name": "Paged retrieval",
      "description": "Implements paging using ldap3's paging helpers (extend.standard.paged_search or SimplePagedResultsControl) with the requested page_size, iterating until the returned cookie is empty and collecting ordered pages.",
      "max_score": 25
    },
    {
      "name": "Connection usage",
      "description": "Obtains ldap3 Connection objects from the factory and uses them for all search operations, ensuring binds/opening and unbind/close (or context manager) are handled through ldap3 APIs rather than custom sockets.",
      "max_score": 15
    }
  ]
}