import org.codelibs.fess.app.service.RoleService;
import org.codelibs.fess.app.service.UserService;
import org.codelibs.fess.app.web.CrudMode;
import org.codelibs.fess.app.web.base.FessAdminAction;
import org.codelibs.fess.app.web.base.login.FessLoginAssist;
import org.codelibs.fess.mylasta.action.FessMessages;
import org.codelibs.fess.opensearch.user.exentity.User;
import org.codelibs.fess.util.ComponentUtil;
import org.codelibs.fess.util.RenderDataUtil;

            validateRequest(ftpClient);

            final FtpAuthentication auth = ftpAuthenticationHolder.get(info.toUrl());
            if (auth != null && !ftpClient.login(auth.getUsername(), auth.getPassword())) {
                throw new CrawlerLoginFailureException("Login Failure: " + auth.getUsername() + " for " + info.toUrl());
            }

            if (enterLocalPassiveMode) {
                ftpClient.enterLocalPassiveMode();

So, you would be able to, for example, share the same data from a Django application in a database with a FastAPI application. Or gradually migrate a Django application using the same database.

And your users would be able to login from your Django app or from your **FastAPI** app, at the same time.

///

## Hash and verify the passwords { #hash-and-verify-the-passwords }

Import the tools we need from `pwdlib`.

Перед развертыванием убедитесь, что вы вошли в систему:

<div class="termy">

```console
$ fastapi login

You are logged in to FastAPI Cloud 🚀
```

</div>

Затем разверните приложение:

<div class="termy">

```console
$ fastapi deploy

Deploying to FastAPI Cloud...

Muitos erros exóticos durante a instalação de um pacote são resolvidos apenas atualizando o `pip` primeiro.

/// tip | Dica

Normalmente, você faria isso **uma vez**, logo após criar o ambiente virtual.

///

Certifique-se de que o ambiente virtual esteja ativo (com o comando acima) e execute:

<div class="termy">

```console
$ python -m pip install --upgrade pip

Provavelmente ainda queremos mantê-lo para o OpenAPI em geral, pois isso garantirá que os IDs de operação sejam **únicos**.

Mas para o cliente gerado, poderíamos **modificar** os IDs de operação do OpenAPI logo antes de gerar os clientes, apenas para tornar esses nomes de método mais agradáveis e **limpos**.

        assertFalse(urlFilter.match("https://example.com/style.css"));
        assertFalse(urlFilter.match("https://example.com/script.js"));
        assertFalse(urlFilter.match("https://example.com/admin/login"));
        assertFalse(urlFilter.match("https://example.com/page#section"));
    }

    /**
     * Test adding invalid regex exclude pattern
     */
    public void test_addExclude_invalidRegex() {

Before deploying, make sure you are logged in:

<div class="termy">

```console
$ fastapi login

You are logged in to FastAPI Cloud 🚀
```

</div>

Then deploy your app:

<div class="termy">

```console
$ fastapi deploy

Deploying to FastAPI Cloud...

Vor dem Deployen, stellen Sie sicher, dass Sie eingeloggt sind:

<div class="termy">

```console
$ fastapi login

You are logged in to FastAPI Cloud 🚀
```

</div>

Dann stellen Sie Ihre App bereit:

<div class="termy">

```console
$ fastapi deploy

Deploying to FastAPI Cloud...

        try (SmbSessionImpl treesess = t.getSession()) {
            if (treesess.getCredentials().isAnonymous() || treesess.getCredentials().isGuest()) {
                // refresh anonymous session or fallback to anonymous from guest login
                try (SmbSessionInternal s =
                        trans.getSmbSession(this.ctx.withAnonymousCredentials(), treesess.getTargetHost(), treesess.getTargetDomain())