- navigation.instant.prefetch
  - navigation.instant.progress
  - navigation.path
  - navigation.tabs
  - navigation.tabs.sticky
  - navigation.top
  - navigation.tracking
  - search.highlight
  - search.share
  - search.suggest
  - toc.follow
  icon:
    repo: fontawesome/brands/github-alt
  logo: img/icon-white.svg
  favicon: img/favicon.png
  language: en
repo_name: fastapi/fastapi

		<groupId>org.codelibs.fess</groupId>
		<artifactId>fess-parent</artifactId>
		<version>15.6.0-SNAPSHOT</version>
		<relativePath />
	</parent>
	<properties>
		<!-- DEB & RPM build -->
		<packaging.fess.home.dir>/usr/share/fess</packaging.fess.home.dir>
		<packaging.fess.app.dir>${packaging.fess.home.dir}/app</packaging.fess.app.dir>
		<packaging.fess.bin.dir>${packaging.fess.home.dir}/bin</packaging.fess.bin.dir>

### 2. Configure WSO2

Once WSO2 is up and running, configure WSO2 to generate Self contained id_tokens. In OAuth 2.0 specification there are primarily two ways to provide id_tokens

1. The id_token is an identifier that is hard to guess. For example, a randomly generated string of sufficient length, that the server handling the protected resource can use to lookup the associated authorization information.

        assertEquals(0x40000000, SmbConstants.GENERIC_WRITE);
        assertEquals(0x80000000, SmbConstants.GENERIC_READ);
    }

    @Test
    @DisplayName("Should define share access constants")
    void testShareAccessConstants() {
        assertEquals(0x00, SmbConstants.FILE_NO_SHARE);
        assertEquals(0x01, SmbConstants.FILE_SHARE_READ);

 * plugin that only runs in the daemon would declare the daemon as a target runtime,
 * while a worker action that executes in a worker must declare that it executes in
 * a worker.
 *
 * However, a shared library used by both daemon and worker actions does not necessarily
 * care which runtimes it must execute in. The target runtimes it must support is a function

                + ",securityMode=0x" + Hexdump.toHexString(this.server.securityMode, 1) + ",security="
                + (this.server.security == SmbConstants.SECURITY_SHARE ? "share" : "user") + ",encryptedPasswords="
                + this.server.encryptedPasswords + ",maxMpxCount=" + this.server.smaxMpxCount + ",maxNumberVcs=" + this.server.maxNumberVcs

Solo la pasas a `Depends` y **FastAPI** sabe cómo hacer el resto.

///

## Compartir dependencias `Annotated` { #share-annotated-dependencies }

En los ejemplos anteriores, ves que hay un poquito de **duplicación de código**.

efficiently makes your stuff load faster and saves bandwidth.

OkHttp is an HTTP client that’s efficient by default:

 * HTTP/2 support allows all requests to the same host to share a socket.
 * Connection pooling reduces request latency (if HTTP/2 isn’t available).
 * Transparent GZIP shrinks download sizes.
 * Response caching avoids the network completely for repeat requests.

OkHttpClient client = new OkHttpClient.Builder()
    .connectionSpecs(Collections.singletonList(spec))
    .build();
```

### Debugging TLS Handshake Failures

The TLS handshake requires clients and servers to share a common TLS version and cipher suite. This
depends on the JVM or Android version, OkHttp version, and web server configuration. If there is no
common cipher suite and TLS version, your call will fail like this:

```

	quarkus/test-framework/junit5-internal/pom.xml
quarkus/integration-tests/reactive-messaging-kafka/pom.xml
	quarkus/integration-tests/class-transformer/runtime/pom.xml
	quarkus/integration-tests/shared-library/pom.xml
	quarkus/extensions/redis-client/runtime/pom.xml
	quarkus/extensions/resteasy-classic/resteasy/runtime/pom.xml
	quarkus/extensions/resteasy-classic/resteasy-jackson/runtime/pom.xml