If there was a query in the request, it will be written to the log in a background task.

And then another background task generated at the *path operation function* will write a message using the `email` path parameter.

## Technical Details { #technical-details }

///

{* ../../docs_src/security/tutorial005_an_py310.py hl[157] *}

## Declare scopes in *path operations* and dependencies { #declare-scopes-in-path-operations-and-dependencies }

Now we declare that the *path operation* for `/users/me/items/` requires the scope `items`.

For this, we import and use `Security` from `fastapi`.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<include path="convention.xml" />
	<include path="lastaflute.xml" />
	
	<!-- Register systemProperties for test environment -->
	<component name="systemProperties" class="org.codelibs.fess.unit.TestSystemProperties" />

    /**
     * Create a new directory cache entry
     *
     * @param path the directory path
     * @param key the lease key
     * @param scope the cache scope
     */
    public DirectoryCacheEntry(String path, Smb2LeaseKey key, DirectoryCacheScope scope) {
        this.directoryPath = path;
        this.leaseKey = key;
        this.scope = scope;
        this.createTime = System.currentTimeMillis();

  - virtual-environments.md
  - Tutorial - User Guide:
    - tutorial/index.md
    - tutorial/first-steps.md
    - tutorial/path-params.md
    - tutorial/query-params.md
    - tutorial/body.md
    - tutorial/query-params-str-validations.md
    - tutorial/path-params-numeric-validations.md
    - tutorial/query-param-models.md
    - tutorial/body-multiple-params.md
    - tutorial/body-fields.md

And all these thousands of *path operations* can be as small as 3 lines:

{* ../../docs_src/security/tutorial002_an_py310.py hl[30:32] *}

## Recap { #recap }

You can now get the current user directly in your *path operation function*.

We are already halfway there.

We just need to add a *path operation* for the user/client to actually send the `username` and `password`.

        /**
         * Create a new change notification handle
         *
         * @param path directory path
         * @param key lease key
         * @param dir directory file
         */
        public ChangeNotificationHandle(String path, Smb2LeaseKey key, SmbFile dir) {
            this.directoryPath = path;
            this.leaseKey = key;
            this.directoryFile = dir;
            this.active = true;

          cp .github/ci-mimir-daemon.properties ~/.mimir/daemon.properties

      - name: Handle Mimir caches
        uses: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809 # v4
        with:
          path: ~/.mimir/local
          key: mimir-${{ runner.os }}-initial-${{ hashFiles('**/pom.xml') }}
          restore-keys: |
            mimir-${{ runner.os }}-initial-
            mimir-${{ runner.os }}-

# Códigos de Estado Adicionales

Por defecto, **FastAPI** devolverá los responses usando un `JSONResponse`, colocando el contenido que devuelves desde tu *path operation* dentro de ese `JSONResponse`.

Usará el código de estado por defecto o el que configures en tu *path operation*.

## Códigos de estado adicionales

# limitations under the License.
# ==============================================================================

name: cffconvert

on:
  push:
    paths:
      - CITATION.cff

permissions:
  contents: read

jobs:
  validate:
    if: github.repository == 'tensorflow/tensorflow' # Don't do this in forks
    name: "validate"
    runs-on: ubuntu-latest