</dependency>

  </dependencies>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <configuration>
          <tasks><echo>${project.parent.basedir}</echo></tasks>
        </configuration>
      </plugin>
    </plugins>
  </build>

    </dependency>

  </dependencies>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <configuration>
          <tasks><echo>${project.parent.basedir}</echo></tasks>
        </configuration>
      </plugin>
    </plugins>
  </build>

import jcifs.smb.SmbNamedPipe;

class CIFSContextWrapperTest {

    private CIFSContext mockDelegate;
    private Configuration mockConfiguration;
    private CIFSContextWrapper cifsContextWrapper;

    @BeforeEach
    void setUp() {
        mockDelegate = mock(CIFSContext.class);
        mockConfiguration = mock(Configuration.class);
        when(mockDelegate.getConfig()).thenReturn(mockConfiguration);

import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

import jcifs.CIFSContext;
import jcifs.Configuration;
import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

@ExtendWith(MockitoExtension.class)
class Smb2LogoffRequestTest {

    @Mock
    Configuration configuration;

    @Mock
    CIFSContext cifsContext;

    // Helper to create a fresh request under test

```

</div>

Y copia el resultado a la variable `SECRET_KEY` (no uses la del ejemplo).

Crea una variable `ALGORITHM` con el algoritmo usado para firmar el token JWT y configúralo a `"HS256"`.

Crea una variable para la expiración del token.

Define un Modelo de Pydantic que se usará en el endpoint de token para el response.

public class Trans2SetFileInformationResponse extends SmbComTransactionResponse {

    /**
     * Constructs a Trans2SetFileInformationResponse with the specified configuration.
     *
     * @param config the SMB configuration
     */
    public Trans2SetFileInformationResponse(final Configuration config) {
        super(config);
        this.setSubCommand(SmbComTransaction.TRANS2_SET_FILE_INFORMATION);
    }

    @Override

      </plugin>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
          <excludes>
            <exclude>**/package-info.java</exclude>
          </excludes>
        </configuration>
      </plugin>
    </plugins>
  </build>

    private final byte expectInfoClass;
    private Decodable info;

    /**
     * Constructs a SMB2 query info response with the specified configuration and expected information types
     *
     * @param config
     *            the configuration to use for this response
     * @param expectInfoType
     *            the expected information type in the response
     * @param expectInfoClass

 * selection to the underlying SSL socket.
 *
 * The configuration of each spec changes with each OkHttp release. This is annoying: upgrading
 * your OkHttp library can break connectivity to certain web servers! But it’s a necessary annoyance
 * because the TLS ecosystem is dynamic and staying up to date is necessary to stay secure. See
 * [OkHttp's TLS Configuration History][tls_history] to track these changes.
 *

    //                                            Entry Page
    //                                            ----------
    /**
     * Displays the form for creating a new duplicate host configuration.
     *
     * @return HTML response for the duplicate host creation form
     */
    @Execute
    @Secured({ ROLE })
    public HtmlResponse createnew() {
        saveToken();