objectClass: inetOrgPerson
cn: Fahim Ahmed
sn: Ahmed
uid: fahim
mail: ******@****.***
userPassword: {SSHA}lRNH+PHooRaruiEb+CBEA21EZLMkAmcc

# Add a user with special chars. The password = example here.
dn: uid=Пользователь,OU=people,OU=swengg,DC=min,DC=io
objectClass: inetOrgPerson
cn: Special Charsman
sn: Charsman
uid: Пользователь
mail: ******@****.***

        * `implicit`
        * `clientCredentials`
        * `authorizationCode`
    * Mas existe um “fluxo” específico que pode ser perfeitamente usado para resolver autenticação diretamente na mesma aplicação:
        * `password`: alguns dos próximos capítulos tratarão disso.
* `openIdConnect`: tem uma forma para definir como descobrir automaticamente o dado da autenticação OAuth2.

                param("env.PERFORMANCE_STAGE", stage.stageName.toString())
                param("env.PERFORMANCE_CHANNEL", performanceTestBuildSpec.channel())
                param("env.PERFORMANCE_DB_PASSWORD_TCAGENT", "%performance.db.password.tcagent%")
                when (os) {
                    Os.WINDOWS -> param("env.PATH", "%env.PATH%;C:/Program Files/7-zip")

                    param("env.HP_HOME_DIR", "/opt/honest-profiler")
                }
            }

            param("env.PERFORMANCE_DB_PASSWORD_TCAGENT", "%performance.db.password.tcagent%")
            param("additional.gradle.parameters", "")
        }

        val buildTypeThis = this
        steps {
            killProcessStep(buildTypeThis, KILL_ALL_GRADLE_PROCESSES, os)

        * `clientCredentials`
        * `authorizationCode`
    * Но есть один конкретный «поток», который можно идеально использовать для обработки аутентификации непосредственно в этом же приложении:
        * `password`: в некоторых следующих главах будут приведены примеры.
* `openIdConnect`: имеет способ определить, как автоматически обнаруживать данные аутентификации OAuth2.

    public static final int ACB_SVRTRUST = 256;
    /** Account control bit flag: Password does not expire */
    public static final int ACB_PWNOEXP = 512;
    /** Account control bit flag: Account is auto-locked */
    public static final int ACB_AUTOLOCK = 1024;
    /** Account control bit flag: Encrypted text password is allowed */
    public static final int ACB_ENC_TXT_PWD_ALLOWED = 2048;

    public static final int ACB_SVRTRUST = 256;
    /** Account control bit flag: Password does not expire */
    public static final int ACB_PWNOEXP = 512;
    /** Account control bit flag: Account is auto-locked */
    public static final int ACB_AUTOLOCK = 1024;
    /** Account control bit flag: Encrypted text password is allowed */
    public static final int ACB_ENC_TXT_PWD_ALLOWED = 2048;

import jcifs.smb1.smb1.NtlmPasswordAuthentication;
import jcifs.smb1.util.Base64;

/**
 * This class is used internally by {@code NtlmHttpFilter},
 * {@code NtlmServlet}, and {@code NetworkExplorer} to negiotiate password
 * hashes via NTLM SSP with MSIE. It might also be used directly by servlet
 * containers to incorporate similar functionality.
 * <p>
 * How NTLMSSP is used in conjunction with HTTP and MSIE clients is

        * `implicit`
        * `clientCredentials`
        * `authorizationCode`
    * Ancak, aynı uygulamanın içinde doğrudan authentication yönetmek için mükemmel şekilde kullanılabilecek özel bir "flow" vardır:
        * `password`: sonraki bazı bölümlerde bunun örnekleri ele alınacak.
* `openIdConnect`: OAuth2 authentication verisinin otomatik olarak nasıl keşfedileceğini tanımlamanın bir yolunu sunar.

Тепер ви можете отримувати поточного користувача безпосередньо у вашій функції операції шляху.

Ми вже на півдорозі.

Потрібно лише додати операцію шляху, щоб користувач/клієнт міг фактично надіслати `username` і `password`.