///

	Um token "bearer" não é a única opção.

	Mas é a melhor no nosso caso.

	E talvez seja a melhor para a maioria dos casos, a não ser que você seja um especialista em OAuth2 e saiba exatamente o porquê de existir outras opções que se adequam melhor às suas necessidades.

	Nesse caso, **FastAPI** também fornece as ferramentas para construir.

			wantKeyNames:   []string{},
		},
		{
			name:   "list keys as user set policy that allows listing but denies specific keys",
			method: http.MethodGet,
			path:   kmsKeyListPath,
			query:  map[string]string{"pattern": "*"},
			asRoot: false,

			// It looks like this should allow listing any key that isn't "default-test-key", however

```JSON
{
  "item": "The Foo Wrestlers"
}
```

But if the client requests `http://example.com/items/bar` (a non-existent `item_id` `"bar"`), that client will receive an HTTP status code of 404 (the "not found" error), and a JSON response of:

```JSON
{
  "detail": "Item not found"
}
```

/// tip

     * We overload this because we want readAndXWireFormat to
     * read the parameter words and bytes. This is so when
     * commands are batched together we can recursivly call
     * readAndXWireFormat without reading the non-existent header.
     */

    @Override
    public int decode(final byte[] buffer, int bufferIndex) throws SMBProtocolDecodingException {
        final int start = this.headerStart = bufferIndex;

        assertTrue(result); // Should still return true even with no matches
    }

    @Test(expected = SuggesterException.class)
    public void testDeleteByQueryWithInvalidIndex() {
        // Test delete with non-existent index
        SuggestUtil.deleteByQuery(client, settings, "nonexistent_index", QueryBuilders.matchAllQuery());
    }

    @Test
    public void testDeleteScrollContext() {

- [ ] Implement directory lease break handling
- [ ] Add directory enumeration caching

#### 4.3 Integration Points
- Extend `SmbFile` for directory lease support
- Modify directory listing operations for caching
- Update change notification handling

---

### Phase 5: RDMA (SMB Direct) Support
**Priority: LOW** | **Estimated Effort: 8-10 weeks**

 * to interact with SMB resources.
 *
 * <p>
 * This client supports authentication, content retrieval, and metadata extraction from SMB files.
 * It handles file access, directory listing, and access control entries (ACEs) processing.
 * </p>
 *
 * <p>
 * The class provides methods to:
 * </p>
 * <ul>
 *   <li>Initialize the client with SMB authentication details.</li>

                    }
                    this.entries[_i].decode(_src);
                }
            }
        }
    }

    /**
     * SAMR EnumerateAliasesInDomain operation for listing aliases in a domain.
     * This operation retrieves a list of alias accounts from the specified domain.
     */
    public static class SamrEnumerateAliasesInDomain extends DcerpcMessage {

        @Override

                    }
                    entries[_i].decode(_src);
                }
            }
        }
    }

    /**
     * SAMR EnumerateAliasesInDomain operation for listing aliases in a domain.
     * This operation retrieves a list of alias accounts from the specified domain.
     */
    public static class SamrEnumerateAliasesInDomain extends DcerpcMessage {

        @Override

	cred, owner, s3Err := validateAdminSignature(ctx, r, "")
	if s3Err != ErrNone {
		writeErrorResponseJSON(ctx, w, errorCodes.ToAPIErr(s3Err), r.URL)
		return
	}

	userDN := r.Form.Get("userDN")

	// If listing is requested for a specific user (who is not the request
	// sender), check that the user has permissions.
	if userDN != "" && userDN != cred.ParentUser {
		if !globalIAMSys.IsAllowed(policy.Args{