private final String targetHost;

    private byte[] preauthIntegrityHash;

    // Multi-channel support
    private ChannelManager channelManager;

    // Witness protocol support fields
    private WitnessClient witnessClient;
    private boolean witnessEnabled;

    // SMB3 lease support
    private LeaseManager leaseManager;

    // SMB3 persistent handle support

import jakarta.servlet.http.HttpServletResponse;
import jakarta.servlet.http.HttpSession;

/**
 * Authenticator for SAML 2.0.
 *
 * <p>This authenticator enables Single Sign-On (SSO) using SAML 2.0 protocol
 * with Identity Providers such as Okta, Azure AD, OneLogin, etc.</p>
 *
 * <h2>Required Configuration</h2>
 * <p>Add the following properties to {@code system.properties}:</p>
 * <pre>
 * # Enable SAML SSO

Estos headers preservan información sobre el request original que de otro modo se perdería:

* **X-Forwarded-For**: La IP original del cliente
* **X-Forwarded-Proto**: El protocolo original (`https`)
* **X-Forwarded-Host**: El host original (`mysuperapp.com`)

            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-main" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-messaging" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-protocol" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-server" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/daemon-services" />

        @Test
        @DisplayName("Should handle negative values in buffer")
        void shouldHandleNegativeValuesInBuffer() throws SMBProtocolDecodingException {
            // Given - negative values (treated as unsigned in protocol)
            ByteBuffer buffer = ByteBuffer.allocate(24);
            buffer.order(ByteOrder.LITTLE_ENDIAN);
            buffer.putLong(-1L);
            buffer.putLong(-1L);
            buffer.putInt(-1);

Persistent handles (also known as durable handles) allow SMB3 connections to survive network disconnections, server reboots, and client reconnections. This feature is critical for enterprise reliability and seamless failover scenarios.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13.2.3**: SMB2_CREATE_DURABLE_HANDLE_REQUEST
- **MS-SMB2 Section 2.2.13.2.4**: SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2

One of:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...and the more exotic ones:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

In the HTTP protocol, you can communicate to each path using one (or more) of these "methods".

---

When building APIs, you normally use these specific HTTP methods to perform a specific action.

Normally you use:

 * Explorer. The users credentials with be negotiated using NTLM SSP if
 * the client is Microsoft Internet Explorer.
 */

/**
 * A servlet that provides network browsing capabilities for SMB shares using SMB1 protocol.
 * This servlet allows users to browse SMB network resources through a web interface.
 */
public class NetworkExplorer extends HttpServlet {

    /**
     * Default constructor.
     */

import jcifs.internal.smb1.com.SmbComTreeConnectAndXResponse;
import jcifs.internal.smb2.tree.Smb2TreeConnectResponse;

/**
 * Test class for TreeConnectResponse interface and its implementations.
 * Tests both SMB1 and SMB2 protocol implementations.
 */
@DisplayName("TreeConnectResponse Tests")
class TreeConnectResponseTest {

    @Mock
    private Configuration mockConfig;

    @BeforeEach
    void setUp() {

 * MA 02111-1307, USA
 */

package jcifs.smb1.util;

import java.io.IOException;
import java.util.Date;

/**
 * Encoding and decoding utility class for SMB1 protocol.
 * Provides methods for encoding/decoding various data types in different byte orders.
 */
public class Encdec {

    /**
     * Default constructor for Encdec.
     * This is a utility class with static methods.