// Then
            verify(transportPool).removeTransport(transport);
            verify(transportPool).removeTransport(transport2);
        }
    }

    @Nested
    @DisplayName("Integration Scenarios")
    class IntegrationTests {

        @Test
        @DisplayName("Should complete full connection lifecycle")
        void testFullConnectionLifecycle() throws Exception {
            // Given

Відкрийте браузер за адресою [http://127.0.0.1:8000](http://127.0.0.1:8000).

Ви побачите JSON-відповідь:

```JSON
{"message": "Hello World"}
```

### Інтерактивна API документація { #interactive-api-docs }

Тепер перейдіть сюди [http://127.0.0.1:8000/docs](http://127.0.0.1:8000/docs).

Ви побачите автоматичну інтерактивну API документацію (надається [Swagger UI](https://github.com/swagger-api/swagger-ui)):

La primera parte de la comunicación es solo para establecer la conexión entre el cliente y el servidor y decidir las claves criptográficas que usarán, etc.

<img src="/img/deployment/https/https02.drawio.svg">

Esta interacción entre el cliente y el servidor para establecer la conexión TLS se llama **handshake TLS**.

### TLS con Extensión SNI { #tls-with-sni-extension }

            Smb2LockResponse response = req.createResponse(mockContext, req);
            assertNotNull(response);
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete lock request workflow")
        void testCompleteLockWorkflow() {

```

该行显示了你的应用在本机所提供服务的 URL 地址。

### 查看 { #check-it }

打开浏览器访问 [http://127.0.0.1:8000](http://127.0.0.1:8000)。

你将看到如下的 JSON 响应：

```JSON
{"message": "Hello World"}
```

### 交互式 API 文档 { #interactive-api-docs }

跳转到 [http://127.0.0.1:8000/docs](http://127.0.0.1:8000/docs)。

你将会看到自动生成的交互式 API 文档（由 [Swagger UI](https://github.com/swagger-api/swagger-ui) 提供）：

# AssumeRoleWithWebIdentity [![Slack](https://slack.min.io/slack?type=svg)](https://slack.min.io)

## Introduction

MinIO supports the standard AssumeRoleWithWebIdentity STS API to enable integration with OIDC/OpenID based identity provider environments. This allows the generation of temporary credentials with pre-defined access policies for applications/users to interact with MinIO object storage.

<img src="/img/tutorial/response-model/image01.png">

Y ambos modelos se utilizarán para la documentación interactiva de la API:

<img src="/img/tutorial/response-model/image02.png">

## Otras Anotaciones de Tipos de Retorno { #other-return-type-annotations }

    @BeforeEach
    void setUp() {
        // Directly set the deferred field on the mock
        mockNdrBuffer.deferred = mockDeferredBuffer;

        // Configure mocks for NdrBuffer interactions
        lenient().when(mockDeferredBuffer.derive(anyInt())).thenReturn(mockDeferredBuffer);
        lenient().doNothing().when(mockDeferredBuffer).advance(anyInt());
        // Set up index field for derive operations

            // Then
            assertEquals(fileFsSizeInfo.getCapacity(), fileFsSizeInfo.getFree());
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should work as AllocInfo implementation")
        void shouldWorkAsAllocInfoImplementation() throws SMBProtocolDecodingException {

<img src="/img/tutorial/response-model/image01.png">

Et les deux modèles seront utilisés pour la documentation API interactive :

<img src="/img/tutorial/response-model/image02.png">

## Autres annotations de type de retour { #other-return-type-annotations }