- Sort Score
- Num 10 results
- Language All
Results 61 - 70 of 130 for beraber (0.04 seconds)
-
docs_src/security/tutorial005_py39.py
security_scopes: SecurityScopes, token: str = Depends(oauth2_scheme) ): if security_scopes.scopes: authenticate_value = f'Bearer scope="{security_scopes.scope_str}"' else: authenticate_value = "Bearer" credentials_exception = HTTPException( status_code=status.HTTP_401_UNAUTHORIZED, detail="Could not validate credentials", headers={"WWW-Authenticate": authenticate_value}, ) try:
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Mon Sep 29 02:57:38 GMT 2025 - 5.3K bytes - Click Count (0) -
docs/ja/docs/tutorial/security/first-steps.md
* したがって、APIで認証するため、HTTPヘッダー`Authorization`に`Bearer`の文字列とトークンを加えた値を送信します。 * トークンに`foobar`が含まれている場合、`Authorization`ヘッダーの内容は次のようになります: `Bearer foobar`。 ## **FastAPI**の`OAuth2PasswordBearer` **FastAPI**は、これらのセキュリティ機能を実装するために、抽象度の異なる複数のツールを提供しています。 この例では、**Bearer**トークンを使用して**OAuth2**を**パスワード**フローで使用します。これには`OAuth2PasswordBearer`クラスを使用します。 /// info | 情報 「bearer」トークンが、唯一の選択肢ではありません。 しかし、私たちのユースケースには最適です。Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Mon Nov 18 02:25:44 GMT 2024 - 10.4K bytes - Click Count (0) -
tests/test_security_oauth2_optional.py
return current_user client = TestClient(app) def test_security_oauth2(): response = client.get("/users/me", headers={"Authorization": "Bearer footokenbar"}) assert response.status_code == 200, response.text assert response.json() == {"username": "Bearer footokenbar"} def test_security_oauth2_password_other_header(): response = client.get("/users/me", headers={"Authorization": "Other footokenbar"})
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Dec 27 18:19:10 GMT 2025 - 8.9K bytes - Click Count (0) -
docs/es/docs/tutorial/security/index.md
* `apiKey`: una clave específica de la aplicación que puede provenir de: * Un parámetro de query. * Un header. * Una cookie. * `http`: sistemas de autenticación HTTP estándar, incluyendo: * `bearer`: un header `Authorization` con un valor de `Bearer ` más un token. Esto se hereda de OAuth2. * Autenticación básica HTTP. * Digest HTTP, etc. * `oauth2`: todas las formas de OAuth2 para manejar la seguridad (llamadas "flujos").
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 10:15:01 GMT 2025 - 4.8K bytes - Click Count (0) -
tests/test_security_oauth2_password_bearer_optional_description.py
assert response.status_code == 200, response.text assert response.json() == {"msg": "Create an account first"} def test_token(): response = client.get("/items", headers={"Authorization": "Bearer testtoken"}) assert response.status_code == 200, response.text assert response.json() == {"token": "testtoken"} def test_incorrect_token():Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Fri Jun 30 18:25:16 GMT 2023 - 2.2K bytes - Click Count (0) -
cmd/batch-expire_test.go
# retainVersions: 5 # keep the latest 5 versions of the object including delete markers. notify: endpoint: https://notify.endpoint # notification endpoint to receive job completion status token: Bearer xxxxx # optional authentication token for the notification endpoint retry: attempts: 10 # number of retries for the job before giving up delay: 500ms # least amount of delay between each retry `Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Thu Aug 01 12:53:30 GMT 2024 - 5.5K bytes - Click Count (0) -
docs/ko/docs/tutorial/security/simple-oauth2.md
`**user_dict`에 대한 자세한 설명은 [**추가 모델** 문서](../extra-models.md#about-user_indict){.internal-link target=_blank}를 다시 읽어봅시다. /// ## 토큰 반환하기 `token` 엔드포인트의 응답은 JSON 객체여야 합니다. `token_type`이 있어야 합니다. 여기서는 "Bearer" 토큰을 사용하므로 토큰 유형은 "`bearer`"여야 합니다. 그리고 액세스 토큰을 포함하는 문자열과 함께 `access_token`이 있어야 합니다. 이 간단한 예제에서는 완전히 안전하지 않고, 동일한 `username`을 토큰으로 반환합니다. /// tip | 팁Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Feb 15 11:19:12 GMT 2025 - 10.8K bytes - Click Count (0) -
docs/de/docs/tutorial/security/oauth2-jwt.md
# OAuth2 mit Passwort (und Hashing), Bearer mit JWT-Tokens { #oauth2-with-password-and-hashing-bearer-with-jwt-tokens } Da wir nun über den gesamten Sicherheitsablauf verfügen, machen wir die Anwendung tatsächlich sicher, indem wir <abbr title="JSON Web Tokens">JWT</abbr>-Tokens und sicheres Passwort-Hashing verwenden. Diesen Code können Sie tatsächlich in Ihrer Anwendung verwenden, die Passwort-Hashes in Ihrer Datenbank speichern, usw.
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Oct 01 15:19:54 GMT 2025 - 12.7K bytes - Click Count (0) -
docs/es/docs/tutorial/security/oauth2-jwt.md
# OAuth2 con Password (y hashing), Bearer con tokens JWT { #oauth2-with-password-and-hashing-bearer-with-jwt-tokens } Ahora que tenemos todo el flujo de seguridad, hagamos que la aplicación sea realmente segura, usando tokens <abbr title="JSON Web Tokens">JWT</abbr> y hashing de contraseñas seguras. Este código es algo que puedes usar realmente en tu aplicación, guardar los hashes de las contraseñas en tu base de datos, etc.
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 16 16:33:45 GMT 2025 - 11.3K bytes - Click Count (0) -
docs/ru/docs/tutorial/security/oauth2-jwt.md
# OAuth2 с паролем (и хешированием), Bearer с JWT-токенами { #oauth2-with-password-and-hashing-bearer-with-jwt-tokens } Теперь, когда у нас определен процесс обеспечения безопасности, давайте сделаем приложение действительно безопасным, используя токены <abbr title="JSON Web Tokens – веб‑токены JSON">JWT</abbr> и безопасное хеширование паролей. Этот код можно реально использовать в своем приложении, сохранять хэши паролей в базе данных и т.д.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Sep 30 11:24:39 GMT 2025 - 19.1K bytes - Click Count (0)