- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 14 for beggarer (0.24 sec)
-
docs/zh/docs/tutorial/security/first-steps.md
- 为指定的端点(Endpoint)进行身份验证 - 因此,用 API 验证身份时,要发送值为 `Bearer` + 令牌的请求头 `Authorization` - 假如令牌为 `foobar`,`Authorization` 请求头就是: `Bearer foobar` ## **FastAPI** 的 `OAuth2PasswordBearer` **FastAPI** 提供了不同抽象级别的安全工具。 本例使用 **OAuth2** 的 **Password** 流以及 **Bearer** 令牌(`Token`)。为此要使用 `OAuth2PasswordBearer` 类。 !!! info "说明" `Bearer` 令牌不是唯一的选择。 但它是最适合这个用例的方案。
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Mar 13 19:02:19 GMT 2024 - 7.4K bytes - Viewed (0) -
docs/em/docs/tutorial/security/first-steps.md
* 🕸 🏪 👈 🤝 🍕 👱. * 👩💻 🖊 🕸 🚶 ➕1️⃣ 📄 🕸 🕸 📱. * 🕸 💪 ☕ 🌅 💽 ⚪️➡️ 🛠️. * ✋️ ⚫️ 💪 🤝 👈 🎯 🔗. * , 🔓 ⏮️ 👆 🛠️, ⚫️ 📨 🎚 `Authorization` ⏮️ 💲 `Bearer ` ➕ 🤝. * 🚥 🤝 🔌 `foobar`, 🎚 `Authorization` 🎚 🔜: `Bearer foobar`. ## **FastAPI**'Ⓜ `OAuth2PasswordBearer` **FastAPI** 🚚 📚 🧰, 🎏 🎚 ⚛, 🛠️ 👫 💂♂ ⚒.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Mar 13 19:02:19 GMT 2024 - 6.8K bytes - Viewed (0) -
docs/em/docs/tutorial/security/oauth2-jwt.md
🚥 👆 📂 👩💻 🧰, 👆 💪 👀 ❔ 📊 📨 🕴 🔌 🤝, 🔐 🕴 📨 🥇 📨 🔓 👩💻 & 🤚 👈 🔐 🤝, ✋️ 🚫 ⏮️: <img src="/img/tutorial/security/image10.png"> !!! note 👀 🎚 `Authorization`, ⏮️ 💲 👈 ▶️ ⏮️ `Bearer `. ## 🏧 ⚙️ ⏮️ `scopes` Oauth2️⃣ ✔️ 🔑 "↔". 👆 💪 ⚙️ 👫 🚮 🎯 ⚒ ✔ 🥙 🤝. ⤴️ 👆 💪 🤝 👉 🤝 👩💻 🔗 ⚖️ 🥉 🥳, 🔗 ⏮️ 👆 🛠️ ⏮️ ⚒ 🚫.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 21:21:35 GMT 2024 - 9.5K bytes - Viewed (0) -
docs/zh/docs/tutorial/security/oauth2-jwt.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 21:21:35 GMT 2024 - 9.2K bytes - Viewed (0) -
common-protos/k8s.io/api/authentication/v1beta1/generated.proto
// +optional optional TokenReviewStatus status = 3; } // TokenReviewSpec is a description of the token authentication request. message TokenReviewSpec { // Token is the opaque bearer token. // +optional optional string token = 1; // Audiences is a list of the identifiers that the resource server presented // with the token identifies as. Audience-aware token authenticators will
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 5.2K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
##### Cluster ```yaml scrape_configs: - job_name: minio-job bearer_token: <secret> metrics_path: /minio/v2/metrics/cluster scheme: http static_configs: - targets: ['localhost:9000'] ``` ##### Bucket centric ```yaml - job_name: minio-job-bucket bearer_token: <secret> metrics_path: /minio/v2/metrics/bucket scheme: http static_configs:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/pt/docs/tutorial/security/first-steps.md
* Mas precisa de autenticação para aquele endpoint em específico. * Então, para autenticar com nossa API, ele manda um header de `Autorização` com o valor `Bearer` mais o token. * Se o token contém `foobar`, o conteúdo do header de `Autorização` será: `Bearer foobar`. ## **FastAPI**'s `OAuth2PasswordBearer` **FastAPI** fornece várias ferramentas, em diferentes níveis de abstração, para implementar esses recursos de segurança.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 8.3K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
* But it needs authentication for that specific endpoint. * So, to authenticate with our API, it sends a header `Authorization` with a value of `Bearer ` plus the token. * If the token contains `foobar`, the content of the `Authorization` header would be: `Bearer foobar`. ## **FastAPI**'s `OAuth2PasswordBearer` **FastAPI** provides several tools, at different levels of abstraction, to implement these security features.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Mar 13 19:02:19 GMT 2024 - 8.9K bytes - Viewed (0) -
docs/zh/docs/tutorial/security/simple-oauth2.md
```Python hl_lines="58-67 69-72 90" {!../../../docs_src/security/tutorial003.py!} ``` !!! info "说明" 此处返回值为 `Bearer` 的响应头 `WWW-Authenticate` 也是规范的一部分。 任何 401**UNAUTHORIZED**HTTP(错误)状态码都应返回 `WWW-Authenticate` 响应头。 本例中,因为使用的是 Bearer Token,该响应头的值应为 `Bearer`。 实际上,忽略这个附加响应头,也不会有什么问题。 之所以在此提供这个附加响应头,是为了符合规范的要求。 说不定什么时候,就有工具用得上它,而且,开发者或用户也可能用得上。 这就是遵循标准的好处……
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 8.8K bytes - Viewed (0) -
docs/fa/docs/tutorial/security/index.md
* شیوه `apiKey`: یک کلید اختصاصی برای برنامه که میتواند از موارد زیر استفاده شود: * پارامتر جستجو. * هدر. * کوکی. * شیوه `http`: سیستمهای استاندارد احراز هویت HTTP، از جمله: * مقدار `bearer`: یک هدر `Authorization` با مقدار `Bearer` به همراه یک توکن. این از OAuth2 به ارث برده شده است. * احراز هویت پایه HTTP. * ویژگی HTTP Digest و غیره. * شیوه `oauth2`: تمام روشهای OAuth2 برای مدیریت امنیت (به نام "flows").
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 23 15:06:11 GMT 2024 - 7.6K bytes - Viewed (0)