}
                }
            } else if (TEARDOWN.equals(step.name)) {
                // TEARDOWN should always run to ensure proper cleanup and error handling
                // We'll handle success/failure reporting inside the TEARDOWN phase
                shouldExecute = true;
            } else {
                // For regular steps:

Ce code est utilisable dans votre application, enregistrez les hachages de mots de passe dans votre base de données, etc.

Nous allons repartir d'où nous nous sommes arrêtés dans le chapitre précédent et l'enrichir.

## À propos de JWT { #about-jwt }

JWT signifie « JSON Web Tokens ».

C'est une norme pour coder un objet JSON dans une longue chaîne compacte sans espaces. Cela ressemble à ceci :

```

            assertEquals(entries1[i].getType(), entries2[i].getType());
            assertEquals(entries2[i].getType(), entries3[i].getType());
        }
    }

    @Test
    @DisplayName("Verify proper inheritance and interface implementation")
    void testInheritance() {
        // Verify MsrpcDfsRootEnum extends netdfs.NetrDfsEnumEx
        assertInstanceOf(netdfs.NetrDfsEnumEx.class, dfsRootEnum);

            }
            break;
        default:
            break;
        }
        return OptionalEntity.empty();
    }

    /**
     * Converts a form to a WebAuthentication entity with proper user and timestamp information.
     *
     * @param form the form containing the web authentication data
     * @return an optional WebAuthentication entity with updated metadata
     */

```

Cela générera un SDK TypeScript dans `./src/client`.

Vous pouvez apprendre à [installer `@hey-api/openapi-ts`](https://heyapi.dev/openapi-ts/get-started) et lire à propos du [résultat généré](https://heyapi.dev/openapi-ts/output) sur leur site.

### Utiliser le SDK { #using-the-sdk }

## Sobre integrações de terceiros { #about-third-party-integrations }

Neste exemplo nós estamos utilizando o fluxo de senha do OAuth2.

Isso é apropriado quando nós estamos autenticando em nossa própria aplicação, provavelmente com o nosso próprio "*frontend*".

Porque nós podemos confiar nele para receber o `username` e o `password`, pois nós controlamos isso.

    // Base64 encoded Type 3 message: NTLMSSP, Type 3
    // User: "user", Domain: "DOMAIN", Workstation: "WORKSTATION"
    // This is a valid Type 3 message with proper structure
    private final String type3MessageBase64 = createValidType3Message();

    /**
     * Creates a valid Type 3 NTLM message for testing
     */
    private static String createValidType3Message() {

                PlexusConfiguration config = XmlPlexusConfiguration.toPlexusConfiguration(dom);
                configProps.put("aether.transport.wagon.config." + server.getId(), config);

                // Translate to proper resolver configuration properties as well (as Plexus XML above is Wagon specific
                // only) but support only configuration/httpConfiguration/all, see

        when(mockTreeHandle.send(any(Smb2WriteRequest.class), any())).thenReturn(mockWriteResponse);
        when(mockWriteResponse.getCount()).thenReturn(10, 5); // Return proper byte counts

        outputStream = new SmbFileOutputStream(mockFile, mockTreeHandle, mockFileHandle,
                SmbConstants.O_CREAT | SmbConstants.O_WRONLY | SmbConstants.O_TRUNC, SmbConstants.FILE_WRITE_DATA,

        assertThrows(SmbException.class, () -> {
            // Control character will be caught in strict mode
            strictValidator.validatePath("//server\u0001/share");
        });

        // Note: Proper UNC validation would require fixing the normalization to preserve \\
        // for UNC paths. Current implementation can't distinguish UNC paths after normalization.
    }

    @Test