- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 171 for secret2 (0.04 seconds)
-
tests/test_response_model_as_return_annotation.py
return DBUser(name="John", surname="Doe", password_hash="secret") @app.get("/response_model_list_of_model-no_annotation", response_model=list[User]) def response_model_list_of_model_no_annotation(): return [ DBUser(name="John", surname="Doe", password_hash="secret"), DBUser(name="Jane", surname="Does", password_hash="secret2"), ]
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Dec 27 12:54:56 GMT 2025 - 47.7K bytes - Click Count (0) -
docs/de/docs/tutorial/security/simple-oauth2.md
} ``` ### Inaktiver Benutzer { #inactive-user } Versuchen Sie es nun mit einem inaktiven Benutzer und authentisieren Sie sich mit: Benutzer: `alice`. Passwort: `secret2`. Und versuchen Sie, die Operation `GET` mit dem Pfad `/users/me` zu verwenden. Sie erhalten die Fehlermeldung „Inactive user“: ```JSON { "detail": "Inactive user" } ```Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Sep 20 15:10:09 GMT 2025 - 11.2K bytes - Click Count (0) -
docs/es/docs/tutorial/security/simple-oauth2.md
```JSON { "detail": "Not authenticated" } ``` ### Usuario inactivo { #inactive-user } Ahora prueba con un usuario inactivo, autentícate con: Usuario: `alice` Contraseña: `secret2` Y trata de usar la operación `GET` con la path `/users/me`. Obtendrás un error de "Usuario inactivo", como: ```JSON { "detail": "Inactive user" } ``` ## Recapitulación { #recap }Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Dec 16 16:33:45 GMT 2025 - 10.3K bytes - Click Count (0) -
docs/pt/docs/tutorial/security/simple-oauth2.md
```JSON { "detail": "Not authenticated" } ``` ### Usuário inativo { #inactive-user } Agora tente com um usuário inativo, autentique-se com: User: `alice` Password: `secret2` E tente usar a operação `GET` com o caminho `/users/me`. Você receberá um erro "Usuário inativo", como: ```JSON { "detail": "Inactive user" } ``` ## Recapitulando { #recap }Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Nov 12 16:23:57 GMT 2025 - 10.3K bytes - Click Count (0) -
docs/ru/docs/tutorial/security/simple-oauth2.md
{ "detail": "Not authenticated" } ``` ### Неактивный пользователь { #inactive-user } Теперь попробуйте с неактивным пользователем, аутентифицируйтесь с: Пользователь: `alice` Пароль: `secret2` И попробуйте использовать операцию `GET` с путём `/users/me`. Вы получите ошибку "Inactive user", как здесь: ```JSON { "detail": "Inactive user" } ``` ## Резюме { #recap }Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Tue Sep 30 11:24:39 GMT 2025 - 16.3K bytes - Click Count (0) -
docs/ko/docs/tutorial/security/simple-oauth2.md
잠금 아이콘을 클릭하고 로그아웃한 다음 동일한 작업을 다시 시도하면 다음과 같은 HTTP 401 오류가 발생합니다. ```JSON { "detail": "Not authenticated" } ``` ### 비활성된 유저 이제 비활성된 사용자로 시도하고, 인증해봅시다: 유저명: `alice` 패스워드: `secret2` 그리고 `/users/me` 경로와 함께 `GET` 작업을 사용해 봅시다. 다음과 같은 "Inactive user" 오류가 발생합니다: ```JSON { "detail": "Inactive user" } ``` ## 요약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) -
helm-releases/minio-3.6.4.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Apr 12 01:30:28 GMT 2022 - 17.9K bytes - Click Count (0) -
helm-releases/minio-4.0.13.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Aug 23 18:18:14 GMT 2022 - 19.5K bytes - Click Count (0) -
helm-releases/minio-4.0.5.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sat Jul 16 06:42:56 GMT 2022 - 18.3K bytes - Click Count (0) -
helm-releases/minio-4.0.8.tgz
displayed in the output of a successful install. ### Existing secret Instead of having this chart create the secret for you, you can supply a preexisting secret, much like an existing PersistentVolumeClai. First, create the secret: ```bash kubectl create secret generic my-minio-secret --from-literal=rootUser=foobarbaz --from-literal=rootPassword=foobarbazqux ``` Then install the chart, specifying that you want to use an existing secret: ```bash helm install --set existingSecret=my-minio-secret minio/minio...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Jul 29 23:39:54 GMT 2022 - 18.6K bytes - Click Count (0)