- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 75 for Muth (0.12 sec)
-
docs/en/docs/advanced/security/http-basic-auth.md
# HTTP Basic Auth For the simplest cases, you can use HTTP Basic Auth. In HTTP Basic Auth, the application expects a header that contains a username and a password. If it doesn't receive it, it returns an HTTP 401 "Unauthorized" error. And returns a header `WWW-Authenticate` with a value of `Basic`, and an optional `realm` parameter. That tells the browser to show the integrated prompt for a username and password.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 14:33:05 GMT 2024 - 5.9K bytes - Viewed (0) -
docs/em/docs/advanced/security/http-basic-auth.md
LeeeeT <******@****.***> 1680341164 +0300
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Apr 01 09:26:04 GMT 2023 - 4.1K bytes - Viewed (0) -
docs/logging/README.md
tls_client_auth (string) clientAuth determines the Kafka server's policy for TLS client auth sasl (on|off) set to 'on' to enable SASL authentication tls (on|off) set to 'on' to enable TLS tls_skip_verify (on|off) trust server TLS without verification, defaults to "on" (verify) client_tls_cert (path) path to client certificate for mTLS auth
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Aug 15 23:04:20 GMT 2023 - 9.9K bytes - Viewed (2) -
common-protos/k8s.io/api/certificates/v1/generated.proto
// // Requests for TLS client certificates typically request: "digital signature", "key encipherment", "client auth". // // Requests for TLS serving certificates typically request: "key encipherment", "digital signature", "server auth". // // Valid values are: // "signing", "digital signature", "content commitment", // "key encipherment", "key agreement", "data encipherment",
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) -
docs/lambda/README.md
Object Lambda ARNs: arn:minio:s3-object-lambda::function:webhook ``` ### Lambda Target with Auth Token If your lambda target expects an authorization token then you can enable it per function target as follows ``` MINIO_LAMBDA_WEBHOOK_ENABLE_function=on MINIO_LAMBDA_WEBHOOK_ENDPOINT_function=http://localhost:5000 MINIO_LAMBDA_WEBHOOK_AUTH_TOKEN="mytoken" minio server /data & ``` ### Lambda Target with mTLS authentication
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Apr 04 19:15:28 GMT 2023 - 7.6K bytes - Viewed (0) -
docs/zh/docs/advanced/security/http-basic-auth.md
# HTTP 基础授权 最简单的用例是使用 HTTP 基础授权(HTTP Basic Auth)。 在 HTTP 基础授权中,应用需要请求头包含用户名与密码。 如果没有接收到 HTTP 基础授权,就返回 HTTP 401 `"Unauthorized"` 错误。 并返回含 `Basic` 值的请求头 `WWW-Authenticate`以及可选的 `realm` 参数。 HTTP 基础授权让浏览器显示内置的用户名与密码提示。 输入用户名与密码后,浏览器会把它们自动发送至请求头。 ## 简单的 HTTP 基础授权 * 导入 `HTTPBsic` 与 `HTTPBasicCredentials` * 使用 `HTTPBsic` 创建**安全概图** * 在*路径操作*的依赖项中使用 `security` * 返回类型为 `HTTPBasicCredentials` 的对象:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 22:43:48 GMT 2024 - 3.9K bytes - Viewed (0) -
ci/official/README.md
# # RBE is incompatible with local caching, so you must remove # disk_cache, public_cache, and public_cache_push from your $TFCI file. # # To use RBE, you must first run `gcloud auth application-default login`, then: export TFCI=py311,linux_x86,rbe # Finally: Run your script of choice. # If you've clicked on a test result from our CI (via a dashboard or GitHub link),
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 8K bytes - Viewed (0) -
docs/sts/keycloak.md
Client ID can be found by clicking any of the clients listed [here](http://localhost:8080/auth/admin/master/console/#/realms/minio/clients). If you have followed the above steps docs, the default Client ID will be `account`. ``` $ go run docs/sts/web-identity.go -cid account -csec 072e7f00-4289-469c-9ab2-bbe843c7f5a8 -config-ep "http://localhost:8080/auth/realms/minio/.well-known/openid-configuration" -port 8888
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 8.1K bytes - Viewed (0) -
README.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 22.6K bytes - Viewed (0) -
docs/ko/docs/tutorial/security/simple-oauth2.md
각 "범위"는 공백이 없는 문자열입니다. 일반적으로 특정 보안 권한을 선언하는 데 사용됩니다. 다음을 봅시다: * `users:read` 또는 `users:write`는 일반적인 예시입니다. * `instagram_basic`은 페이스북/인스타그램에서 사용합니다. * `https://www.googleapis.com/auth/drive`는 Google에서 사용합니다. !!! 정보 OAuth2에서 "범위"는 필요한 특정 권한을 선언하는 문자열입니다. `:`과 같은 다른 문자가 있는지 또는 URL인지는 중요하지 않습니다. 이러한 세부 사항은 구현에 따라 다릅니다. OAuth2의 경우 문자열일 뿐입니다.
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)