And all of them will use the same WebSocket connection.

## Using `Depends` and others { #using-depends-and-others }

In WebSocket endpoints you can import from `fastapi` and use:

* `Depends`
* `Security`
* `Cookie`
* `Header`
* `Path`
* `Query`

They work the same way as for other FastAPI endpoints/*path operations*:

{* ../../docs_src/websockets_/tutorial002_an_py310.py hl[68:69,82] *}

          "build-cache-example-client",
          "client-services",
          "composite-builds",
          "docs",
          "files",
          "model-reflect",
          "request-handler-worker",
          "security",
          "service-registry-impl",
          "stdlib-java-extensions",
          "tooling-api-builders"
        ],
        "parallelizationMethod": {
          "name": "TestDistribution"
        }
      },

        assertTrue(stringRep.contains("DOMAIN"));
        assertTrue(stringRep.contains("WORKSTATION"));
    }

    @Test
    @DisplayName("Should handle extended security flags")
    void testExtendedSecurityFlags() {
        // Given
        int extendedFlags = NtlmFlags.NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY;

        // When

     * for "Share Permissions" and another for "Security". These correspond to
     * the ACLs returned by {@code getShareSecurity} and {@code getSecurity}
     * respectively.
     * @param resolveSids Attempt to resolve the SIDs within each ACE form
     * their numeric representation to their corresponding account names.
     */
    /**
     * Returns the share security information for this share
     *

Using Linux containers has several advantages including **security**, **replicability**, **simplicity**, and others.

/// tip

In a hurry and already know this stuff? Jump to the [`Dockerfile` below 👇](#build-a-docker-image-for-fastapi).

///

<details>

    * [fluentd-gcp addon] Bump fluentd-gcp-scaler to v0.5.1 to pick up security fixes.
    * [fluentd-gcp addon] Bump event-exporter to v0.2.4 to pick up security fixes.
    * [fluentd-gcp addon] Bump prometheus-to-sd to v0.5.0 to pick up security fixes.

# MinIO STS Quickstart Guide [![Slack](https://slack.min.io/slack?type=svg)](https://slack.min.io)

The MinIO Security Token Service (STS) is an endpoint service that enables clients to request temporary credentials for MinIO resources. Temporary credentials work almost identically to default admin credentials, with some differences:

    - [Server Binaries](#server-binaries)
    - [Node Binaries](#node-binaries)
    - [Container Images](#container-images)
  - [Changelog since v1.27.15](#changelog-since-v12715)
  - [Important Security Information](#important-security-information)
    - [CVE-2024-5321: Incorrect permissions on Windows containers logs](#cve-2024-5321-incorrect-permissions-on-windows-containers-logs)
  - [Changes by Kind](#changes-by-kind)
    - [Feature](#feature)

- **Concurrent Utilities** (`org.codelibs.core.concurrent`) - Thread-safe collections and concurrency helpers using modern concurrent APIs
- **Crypto & Security** (`org.codelibs.core.crypto`, `org.codelibs.core.security`) - Basic cryptographic utilities, message digest operations, and secure random generation
- **XML Processing** (`org.codelibs.core.xml`) - XML DOM utilities, SAX parser helpers, and schema validation support

> NOTE: make sure your AD/Windows user has write permissions to *D:\data* prior to using `credentialspec=`.

```powershell
docker run \
  -p 9000:9000 \
  -p 9001:9001 \
  --name minio1 \
  --security-opt "credentialspec=file://myuser.json"
  -e "MINIO_ROOT_USER=AKIAIOSFODNN7EXAMPLE" \
  -e "MINIO_ROOT_PASSWORD=wJalrXUtnFEMIK7MDENGbPxRfiCYEXAMPLEKEY" \
  -v D:\data:/data \