*/
package jcifs.internal.smb2.lease;

import jcifs.internal.smb2.create.CreateContextRequest;
import jcifs.internal.util.SMBUtil;

/**
 * Directory Lease Context for SMB3 directory leasing
 *
 * This context extends standard lease context with directory-specific metadata
 * for enhanced directory caching capabilities.
 */
public class DirectoryLeaseContext implements CreateContextRequest {

        testBuffer[8] = 0x01; // Revision
        testBuffer[9] = 0x01; // Sub-authority count
        testBuffer[10] = 0x00; // Identifier authority
        testBuffer[11] = 0x00;
        testBuffer[12] = 0x00;
        testBuffer[13] = 0x00;
        testBuffer[14] = 0x00;
        testBuffer[15] = 0x01;
        testBuffer[16] = 0x00; // Sub-authority
        testBuffer[17] = 0x00;
        testBuffer[18] = 0x00;

import jcifs.internal.smb2.info.Smb2QueryInfoRequest;
import jcifs.internal.smb2.info.Smb2SetInfoRequest;
import jcifs.internal.smb2.io.Smb2ReadRequest;
import jcifs.internal.smb2.io.Smb2WriteRequest;

/**
 * Load balancer for SMB3 Multi-Channel connections
 */
public class ChannelLoadBalancer {

    private final ChannelManager manager;
    private LoadBalancingStrategy strategy;
    private final AtomicInteger roundRobinCounter;

    /**

import jcifs.Configuration;
import jcifs.config.PropertyConfiguration;
import jcifs.internal.smb2.ServerMessageBlock2Request;
import jcifs.smb.SmbSessionInternal;
import jcifs.smb.SmbTransportInternal;

/**
 * Unit tests for SMB3 Multi-Channel functionality
 *
 * These tests verify the multi-channel implementation without requiring a real SMB server.
 */
@ExtendWith(MockitoExtension.class)
@MockitoSettings(strictness = Strictness.LENIENT)

Create a real JWT access token and return it.

{* ../../docs_src/security/tutorial004_an_py310.py hl[118:133] *}

### Technical details about the JWT "subject" `sub` { #technical-details-about-the-jwt-subject-sub }

The JWT specification says that there's a key `sub`, with the subject of the token.

It's optional to use it, but that's where you would put the user's identification, so we are using it here.

Deshalb, um ID-Kollisionen zu vermeiden, könnten Sie beim Erstellen des JWT-Tokens für den Benutzer, dem Wert des `sub`-Schlüssels ein Präfix, z. B. `username:` voranstellen. In diesem Beispiel hätte der Wert von `sub` also auch `username:johndoe` sein können.

Der wesentliche Punkt ist, dass der `sub`-Schlüssel in der gesamten Anwendung eine eindeutige Kennung haben sollte, und er sollte ein String sein.

## Es testen

Entonces, para evitar colisiones de ID, cuando crees el token JWT para el usuario, podrías prefijar el valor de la clave `sub`, por ejemplo, con `username:`. Así, en este ejemplo, el valor de `sub` podría haber sido: `username:johndoe`.

Lo importante a tener en cuenta es que la clave `sub` debería tener un identificador único a lo largo de toda la aplicación, y debería ser un string.

## Revisa

            cipherId = EncryptionNegotiateContext.CIPHER_AES128_CCM;
        } else {
            throw new SmbUnsupportedOperationException("SMB3 required for encryption, negotiated: " + dialect);
        }

        try {
            // Derive encryption and decryption keys using SMB3 KDF
            final int dialectInt = dialect.getDialect();

	SUB	$0x000aaa, R2, R3               // SUB $2730, R2, R3                      // 43a82ad1
	SUB	$0x000aaa, R2                   // SUB $2730, R2                          // 42a82ad1
	SUB	$0xaaa000, R2, R3               // SUB $11182080, R2, R3                  // 43a86ad1
	SUB	$0xaaa000, R2                   // SUB $11182080, R2                      // 42a86ad1

Including how to handle lifespan state that can be used in other areas of your code.

///

## Sub Applications { #sub-applications }