- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 28 for UserName (0.15 sec)
-
docs/de/docs/tutorial/security/simple-oauth2.md
## `username` und `password` entgegennehmen Wir werden **FastAPIs** Sicherheits-Werkzeuge verwenden, um den `username` und das `password` entgegenzunehmen. OAuth2 spezifiziert, dass der Client/Benutzer bei Verwendung des „Password Flow“ (den wir verwenden) die Felder `username` und `password` als Formulardaten senden muss.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 18:08:44 GMT 2024 - 14.3K bytes - Viewed (0) -
docs/en/docs/tutorial/security/simple-oauth2.md
Now let's build from the previous chapter and add the missing parts to have a complete security flow. ## Get the `username` and `password` We are going to use **FastAPI** security utilities to get the `username` and `password`. OAuth2 specifies that when using the "password flow" (that we are using) the client/user must send a `username` and `password` fields as form data.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 12.5K bytes - Viewed (0) -
docs/ko/docs/tutorial/security/simple-oauth2.md
# 패스워드와 Bearer를 이용한 간단한 OAuth2 이제 이전 장에서 빌드하고 누락된 부분을 추가하여 완전한 보안 흐름을 갖도록 하겠습니다. ## `username`와 `password` 얻기 **FastAPI** 보안 유틸리티를 사용하여 `username` 및 `password`를 가져올 것입니다. OAuth2는 (우리가 사용하고 있는) "패스워드 플로우"을 사용할 때 클라이언트/유저가 `username` 및 `password` 필드를 폼 데이터로 보내야 함을 지정합니다. 그리고 사양에는 필드의 이름을 그렇게 지정해야 한다고 나와 있습니다. 따라서 `user-name` 또는 `email`은 작동하지 않습니다. 하지만 걱정하지 않아도 됩니다. 프런트엔드에서 최종 사용자에게 원하는 대로 표시할 수 있습니다. 그리고 데이터베이스 모델은 원하는 다른 이름을 사용할 수 있습니다.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Apr 02 22:37:23 GMT 2024 - 11.6K bytes - Viewed (0) -
docs/ru/docs/tutorial/extra-models.md
```Python UserInDB( username="john", password="secret", email="******@****.***", full_name=None, ) ``` Или, если для большей точности мы напрямую используем `user_dict` с любым потенциальным содержимым, то этот пример будет выглядеть так: ```Python UserInDB( username = user_dict["username"], password = user_dict["password"], email = user_dict["email"],
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 11.6K bytes - Viewed (0) -
docs/de/docs/tutorial/security/first-steps.md
Betrachten wir es also aus dieser vereinfachten Sicht: * Der Benutzer gibt den `username` und das `password` im Frontend ein und drückt `Enter`. * Das Frontend (das im Browser des Benutzers läuft) sendet diesen `username` und das `password` an eine bestimmte URL in unserer API (deklariert mit `tokenUrl="token"`). * Die API überprüft den `username` und das `password` und antwortet mit einem „Token“ (wir haben davon noch nichts implementiert).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 18:07:08 GMT 2024 - 10.3K bytes - Viewed (0) -
docs/en/docs/tutorial/security/oauth2-jwt.md
So, to avoid ID collisions, when creating the JWT token for the user, you could prefix the value of the `sub` key, e.g. with `username:`. So, in this example, the value of `sub` could have been: `username:johndoe`. The important thing to keep in mind is that the `sub` key should have a unique identifier across the entire application, and it should be a string. ## Check it
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 13K bytes - Viewed (0) -
docs/zh/docs/advanced/security/oauth2-scopes.md
{!../../../docs_src/security/tutorial005.py!} ``` ## 校验 `username` 与数据形状 我们可以校验是否获取了 `username`,并抽取作用域。 然后,使用 Pydantic 模型校验数据(捕获 `ValidationError` 异常),如果读取 JWT 令牌或使用 Pydantic 模型验证数据时出错,就会触发之前创建的 `HTTPException` 异常。 对此,要使用新的属性 `scopes` 更新 Pydantic 模型 `TokenData`。 使用 Pydantic 验证数据可以确保数据中含有由作用域组成的**字符串列表**,以及 `username` 字符串等内容。 反之,如果使用**字典**或其它数据结构,就有可能在后面某些位置破坏应用,形成安全隐患。
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 22:43:35 GMT 2024 - 11.8K bytes - Viewed (0) -
docs/de/docs/tutorial/security/oauth2-jwt.md
Deshalb, um ID-Kollisionen zu vermeiden, könnten Sie beim Erstellen des JWT-Tokens für den Benutzer, dem Wert des `sub`-Schlüssels ein Präfix, z. B. `username:` voranstellen. In diesem Beispiel hätte der Wert von `sub` also auch `username:johndoe` sein können. Der wesentliche Punkt ist, dass der `sub`-Schlüssel in der gesamten Anwendung eine eindeutige Kennung haben sollte, und er sollte ein String sein. ## Es testen
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 20:27:06 GMT 2024 - 15.1K bytes - Viewed (0) -
docs/ru/docs/tutorial/body-multiple-params.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 11.7K bytes - Viewed (0) -
common-protos/k8s.io/api/certificates/v1/generated.proto
// "timestamping", "ocsp signing", "microsoft sgc", "netscape sgc" // +listType=atomic repeated string usages = 5; // username contains the name of the user that created the CertificateSigningRequest. // Populated by the API server on creation and immutable. // +optional optional string username = 2; // uid contains the uid of the user that created the CertificateSigningRequest.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 11.6K bytes - Viewed (0)