import org.apache.maven.wagon.OutputData;
import org.apache.maven.wagon.ResourceDoesNotExistException;
import org.apache.maven.wagon.StreamWagon;
import org.apache.maven.wagon.TransferFailedException;
import org.apache.maven.wagon.authentication.AuthenticationException;
import org.apache.maven.wagon.authorization.AuthorizationException;
import org.apache.maven.wagon.resource.Resource;

@Named("string")
@Singleton
public class StringWagon extends StreamWagon {

This is very useful when you need to:

* Have shared logic (the same code logic again and again).
* Share database connections.
* Enforce security, authentication, role requirements, etc.
* And many other things...

All these, while minimizing code repetition.

## First Steps { #first-steps }

        // Should be an error status (0xC prefix)
        assertTrue((status & (int) 0xC0000000L) == (int) 0xC0000000L);
    }

    @Test
    @DisplayName("Should handle authentication failure status")
    void testAuthenticationFailureStatus() {
        // Given
        int status = NtStatus.NT_STATUS_LOGON_FAILURE;

        // When/Then
        assertEquals((int) 0xC000006DL, status);

import jcifs.CIFSException;

/**
 * Security Support Provider (SSP) context.
 *
 * This interface provides context for security support provider
 * operations during SMB authentication.
 *
 * @author mbechler
 */
public interface SSPContext {

    /**
     * Gets the signing key for the session.
     * @return the signing key for the session

If you integrate your API with an OAuth2 provider, you will be able to authenticate and come back to the API docs with the acquired credentials. And interact with it using the real OAuth2 authentication.

Swagger UI will handle it behind the scenes for you, but it needs this "redirect" helper.

///

### Create a *path operation* to test it { #create-a-path-operation-to-test-it }

### Use cases: external service { #use-cases-external-service }

An example could be that you have an external authentication provider that you need to call.

You send it a token and it returns an authenticated user.

Use `Response.challenges()` to get the schemes and realms of any authentication challenges. When fulfilling a `Basic` challenge, use `Credentials.basic(username, password)` to encode the request header.

=== ":material-language-kotlin: Kotlin"
    ```kotlin
      private val client = OkHttpClient.Builder()
          .authenticator(object : Authenticator {
            @Throws(IOException::class)

        }
    }

    /**
     * Resolves an array of SIDs to obtain their account and domain names.
     *
     * @param authorityServerName the server to use for SID resolution
     * @param auth the authentication credentials to use
     * @param sids the array of SIDs to resolve
     * @param offset the starting offset in the array
     * @param length the number of SIDs to resolve

import org.junit.jupiter.api.Nested;
import org.junit.jupiter.api.Test;

/**
 * Test suite for jcifs.smb1.https.Handler class.
 * Tests HTTPS URL stream handler functionality with NTLM authentication support.
 */
@DisplayName("SMB1 HTTPS Handler Tests")
class HandlerTest {

    private Handler handler;

    @BeforeEach
    void setUp() {
        handler = new Handler();
    }

    @Nested

import org.bouncycastle.asn1.DERBitString;

import jcifs.pac.ASN1Util;
import jcifs.pac.PACDecodingException;

/**
 * Represents a Kerberos AP-REQ (Application Request) message.
 * This class parses and contains the authentication request sent from a client to a server.
 */
public class KerberosApRequest {

    private byte apOptions;
    private KerberosTicket ticket;

    /**
     * Creates a Kerberos AP request from a token.