- Sort Score
- Result 10 results
- Languages All
Results 161 - 170 of 275 for beraber (0.19 sec)
-
docs/ru/docs/tutorial/cors.md
Но тогда не будут разрешены некоторые виды взаимодействия, включая всё связанное с учётными данными: куки, заголовки Authorization с Bearer-токенами наподобие тех, которые мы использовали ранее и т.п. Поэтому, чтобы всё работало корректно, лучше явно указывать список разрешённых источников. ## Использование `CORSMiddleware`
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Jun 22 14:29:56 UTC 2023 - 8.3K bytes - Viewed (0) -
bin/init.sh
# If we are not using the default, assume its private and we need to authenticate if [[ "${ISTIO_ENVOY_BASE_URL}" != "https://storage.googleapis.com/istio-build/proxy" ]]; then AUTH_HEADER="Authorization: Bearer $(gcloud auth print-access-token)" export AUTH_HEADER fi SIDECAR="${SIDECAR:-envoy}" # OS-neutral vars. These currently only work for linux. ISTIO_ENVOY_VERSION="${ISTIO_ENVOY_VERSION:-${PROXY_REPO_SHA}}"
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Jan 25 19:11:31 UTC 2024 - 6.1K bytes - Viewed (0) -
docs/batch-jobs/README.md
# value: "image/*" # match objects with 'content-type', with all values starting with 'image/' notify: endpoint: "https://notify.endpoint" # notification endpoint to receive job status events 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 ```
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Thu Oct 06 06:00:43 UTC 2022 - 4.8K bytes - Viewed (0) -
common-protos/k8s.io/api/authentication/v1beta1/generated.proto
// +optional optional TokenReviewStatus status = 3; } // TokenReviewSpec is a description of the token authentication request. message TokenReviewSpec { // Token is the opaque bearer token. // +optional optional string token = 1; // Audiences is a list of the identifiers that the resource server presented // with the token identifies as. Audience-aware token authenticators will
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 5.2K bytes - Viewed (0) -
staging/src/k8s.io/api/authentication/v1beta1/generated.proto
// +optional optional TokenReviewStatus status = 3; } // TokenReviewSpec is a description of the token authentication request. message TokenReviewSpec { // Token is the opaque bearer token. // +optional optional string token = 1; // Audiences is a list of the identifiers that the resource server presented // with the token identifies as. Audience-aware token authenticators will
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Thu Mar 28 15:34:11 UTC 2024 - 5.3K bytes - Viewed (0) -
api/openapi-spec/v3/apis_openapi.json
"required": [ "clientCIDR", "serverAddress" ], "type": "object" } }, "securitySchemes": { "BearerToken": { "description": "Bearer Token authentication", "in": "header", "name": "authorization", "type": "apiKey" } } }, "info": { "title": "Kubernetes", "version": "unversioned"
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Mon Nov 27 20:05:52 UTC 2023 - 7.8K bytes - Viewed (0) -
docs/en/docs/tutorial/cors.md
But that will only allow certain types of communication, excluding everything that involves credentials: Cookies, Authorization headers like those used with Bearer Tokens, etc. So, for everything to work correctly, it's better to specify explicitly the allowed origins. ## Use `CORSMiddleware` You can configure it in your **FastAPI** application using the `CORSMiddleware`.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sun Nov 13 20:28:37 UTC 2022 - 5.1K bytes - Viewed (0) -
docs/en/docs/tutorial/security/oauth2-jwt.md
# OAuth2 with Password (and hashing), Bearer with JWT tokens Now that we have all the security flow, let's make the application actually secure, using <abbr title="JSON Web Tokens">JWT</abbr> tokens and secure password hashing. This code is something you can actually use in your application, save the password hashes in your database, etc. We are going to start from where we left in the previous chapter and increment it. ## About JWT
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Mon May 20 17:37:28 UTC 2024 - 12.7K bytes - Viewed (0) -
docs/zh/docs/tutorial/security/oauth2-jwt.md
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Jan 11 21:21:35 UTC 2024 - 9.2K bytes - Viewed (0) -
docs/de/docs/tutorial/security/oauth2-jwt.md
# OAuth2 mit Password (und Hashing), Bearer mit 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. Wir bauen auf dem vorherigen Kapitel auf. ## Über JWT
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat Mar 30 20:27:06 UTC 2024 - 15.1K bytes - Viewed (0)