Properties props = new Properties();
        // Set some default test properties
        props.setProperty("jcifs.smb.client.username", "testuser");
        props.setProperty("jcifs.smb.client.password", "testpass");
        props.setProperty("jcifs.smb.client.domain", "testdomain");
        props.setProperty("jcifs.netbios.hostname", "testhost");
        props.setProperty("jcifs.netbios.scope", "");

        * `implicit`
        * `clientCredentials`
        * `authorizationCode`
    * 하지만 같은 애플리케이션에서 직접 인증을 처리하는 데 완벽하게 사용할 수 있는 특정 "flow"도 하나 있습니다:
        * `password`: 다음 장들에서 이에 대한 예시를 다룹니다.
* `openIdConnect`: OAuth2 인증 데이터를 자동으로 탐색(discover)하는 방법을 정의합니다.
    * 이 자동 탐색은 OpenID Connect 명세에서 정의됩니다.


/// tip | 팁

annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 resources: requests: memory: 128Mi nodeSelector: {} tolerations: [] affinity: {} ## List of users to be created after minio install ## users: ## Username, password and policy to be assigned to the user ## Default policies are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will fail if...

    private static final int NETBIOS_PORT = 139;

    private static final String WORKGROUP = "WORKGROUP";
    private static final String USERNAME = "smbuser";
    private static final String PASSWORD = "smbpass";

    private Path tempDir;
    private String baseUrl;
    private CIFSContext context;

    @Container
    static GenericContainer<?> sambaContainer;

    static {

Agora você pode obter o usuário atual diretamente na sua *função de operação de rota*.

Já estamos na metade do caminho.

Só precisamos adicionar uma *operação de rota* para que o usuário/cliente realmente envie o `username` e `password`.

                buffer.append(hash).append('@');
            }
            buffer.append(proxy.getHost()).append(':').append(proxy.getPort()).append('>');
        }

        // consider the username&password because a repo manager might block artifacts depending on authorization
        Authentication auth = repository.getAuthentication();
        if (auth != null) {

    * 其中數個 flow 適合用來建立 OAuth 2.0 身分驗證提供者（如 Google、Facebook、X（Twitter）、GitHub 等）：
        * `implicit`
        * `clientCredentials`
        * `authorizationCode`
    * 但有一個特定的 flow 可直接在同一個應用中處理身分驗證：
        * `password`：後續幾個章節會示範這個。
* `openIdConnect`：提供一種方式來定義如何自動發現 OAuth2 的身分驗證資訊。
    * 這種自動探索機制即由 OpenID Connect 規範定義。

/// tip | 提示
整合像 Google、Facebook、X（Twitter）、GitHub 等其他身分驗證/授權提供者也是可行而且相對容易。

@REM Apache Maven Wrapper startup batch script, version 3.3.4
@REM
@REM Optional ENV vars
@REM   MVNW_REPOURL - repo url base for downloading maven distribution
@REM   MVNW_USERNAME/MVNW_PASSWORD - user and password for downloading maven
@REM   MVNW_VERBOSE - true: enable verbose log; others: silence the output
@REM ----------------------------------------------------------------------------

Nous avons déjà fait la moitié du chemin.

Il nous suffit d'ajouter un *chemin d'accès* pour que l'utilisateur/client envoie effectivement le `username` et le `password`.

        * `clientCredentials`
        * `authorizationCode`
    * Mais il existe un « flow » spécifique qui peut parfaitement être utilisé pour gérer l'authentification directement dans la même application :
        * `password` : certains des prochains chapitres couvriront des exemples à ce sujet.
* `openIdConnect` : propose un moyen de définir comment découvrir automatiquement les données d'authentification OAuth2.