- Sort Score
- Num 10 results
- Language All
Results 551 - 560 of 639 for USERNAME (0.07 seconds)
-
cmd/testdata/undeleteable-object.tgz
ueue_dir","value":""}]},"notify_elasticsearch":{"_":[{"key":"enable","value":"off"},{"key":"url","value":""},{"key":"format","value":"namespace"},{"key":"index","value":""},{"key":"queue_dir","value":""},{"key":"queue_limit","value":"0"},{"key":"username","value":""},{"key":"password","value":""}]},"notify_kafka":{"_":[{"key":"enable","value":"off"},{"key":"topic","value":""},{"key":"brokers","value":""},{"key":"sasl_username","value":""},{"key":"sasl_password","value":""},{"key":"sasl_mechanism...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Apr 26 00:31:12 GMT 2024 - 8.7M bytes - Click Count (0) -
docs/uk/docs/tutorial/security/oauth2-jwt.md
Використайте облікові дані: Username: `johndoe` Password: `secret` /// check | Перевірте Зверніть увагу, що ніде в коді немає відкритого пароля "`secret`", ми маємо лише хешовану версію. /// <img src="/img/tutorial/security/image08.png"> Викличте кінцеву точку `/users/me/`, ви отримаєте відповідь: ```JSON { "username": "johndoe", "email": "******@****.***",
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:27:41 GMT 2026 - 17.9K bytes - Click Count (0) -
docs/ko/docs/tutorial/security/oauth2-jwt.md
이전과 같은 방법으로 애플리케이션을 인가하십시오. 다음 인증 정보를 사용하십시오: Username: `johndoe` Password: `secret` /// check | 확인 코드 어디에도 평문 패스워드 "`secret`"은 없고, 해시된 버전만 있다는 점에 유의하십시오. /// <img src="/img/tutorial/security/image08.png"> 엔드포인트 `/users/me/`를 호출하면 다음과 같은 응답을 받게 됩니다: ```JSON { "username": "johndoe", "email": "******@****.***", "full_name": "John Doe",
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 14:06:26 GMT 2026 - 13K bytes - Click Count (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.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 17:58:09 GMT 2026 - 12.9K bytes - Click Count (0) -
docs/es/docs/tutorial/security/oauth2-jwt.md
Entonces, para evitar colisiones de ID, cuando crees el token JWT para el usuario, podrías prefijar el valor de la clave `sub`, por ejemplo, con `username:`. Así, en este ejemplo, el valor de `sub` podría haber sido: `username:johndoe`. Lo importante a tener en cuenta es que la clave `sub` debería tener un identificador único a lo largo de toda la aplicación, y debería ser un string.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:15:55 GMT 2026 - 11.5K bytes - Click Count (0) -
docs/uk/docs/tutorial/request-form-models.md
{* ../../docs_src/request_form_models/tutorial002_an_py310.py hl[12] *} Якщо клієнт спробує надіслати додаткові дані, він отримає **відповідь з помилкою**. Наприклад, якщо клієнт спробує надіслати поля форми: * `username`: `Rick` * `password`: `Portal Gun` * `extra`: `Mr. Poopybutthole` Він отримає відповідь із помилкою, яка повідомляє, що поле `extra` не дозволено: ```json { "detail": [ {Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:27:41 GMT 2026 - 3.2K bytes - Click Count (0) -
src/archive/tar/stat_unix.go
// (not implemented on that platform, cgo not enabled, etc). if u, ok := userMap.Load(h.Uid); ok { h.Uname = u.(string) } else if u, err := user.LookupId(strconv.Itoa(h.Uid)); err == nil { h.Uname = u.Username userMap.Store(h.Uid, h.Uname) } if g, ok := groupMap.Load(h.Gid); ok { h.Gname = g.(string) } else if g, err := user.LookupGroupId(strconv.Itoa(h.Gid)); err == nil { h.Gname = g.Name
Created: Tue Apr 07 11:13:11 GMT 2026 - Last Modified: Tue Dec 30 15:28:53 GMT 2025 - 3.2K bytes - Click Count (0) -
helm-releases/minio-5.2.0.tgz
makePolicyJob makePolicyJob: securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 resources: requests: memory: 128Mi # Command to run after the main command on exit exitCommand: "" ## List of users to be created after minio install ## users: ## Username, password and policy to be assigned to the user ## Default policies are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://min.io/docs/minio/kubernetes/upstream/administration/identity-access-ma...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Apr 28 10:14:37 GMT 2024 - 21.7K bytes - Click Count (0) -
docs/pt/docs/tutorial/request-form-models.md
Caso um cliente tente enviar informações adicionais, ele receberá um retorno de **erro**. Por exemplo, se o cliente tentar enviar os campos de formulário: * `username`: `Rick` * `password`: `Portal Gun` * `extra`: `Mr. Poopybutthole` Ele receberá um retorno de erro informando-o que o campo `extra` não é permitido: ```json { "detail": [ {Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:20:43 GMT 2026 - 2.4K bytes - Click Count (0) -
helm-releases/minio-4.0.6.tgz
podAnnotations: annotations: securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 resources: requests: memory: 128Mi nodeSelector: {} tolerations: [] affinity: {} ## List of users to be created after minio install ## users: ## Username, password and policy to be assigned to the user ## Default policies are [readonly|readwrite|writeonly|consoleAdmin|diagnostics] ## Add new policies as explained here https://docs.min.io/docs/minio-multi-user-quickstart-guide.html ## NOTE: this will...Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Jul 24 03:34:14 GMT 2022 - 18.4K bytes - Click Count (0)