- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 93 for authorization (0.08 sec)
-
fastapi/security/http.py
async def __call__( self, request: Request ) -> Optional[HTTPAuthorizationCredentials]: authorization = request.headers.get("Authorization") scheme, credentials = get_authorization_scheme_param(authorization) if not (authorization and scheme and credentials): if self.auto_error: raise HTTPException(
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Thu Sep 19 09:47:28 UTC 2024 - 13.2K bytes - Viewed (0) -
fastapi/security/oauth2.py
authorization = request.headers.get("Authorization") if not authorization: if self.auto_error: raise HTTPException( status_code=HTTP_403_FORBIDDEN, detail="Not authenticated" ) else: return None return authorization class OAuth2PasswordBearer(OAuth2): """
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Wed Oct 23 18:30:18 UTC 2024 - 21.1K bytes - Viewed (0) -
cmd/jwt_test.go
expectedErr error }{ // Set valid authorization header. { req: &http.Request{ Header: http.Header{ "Authorization": []string{token}, }, }, expectedErr: nil, }, // No authorization header. { req: &http.Request{ Header: http.Header{}, }, expectedErr: errNoAuthToken, }, // Invalid authorization token. { req: &http.Request{
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Jul 22 07:04:48 UTC 2024 - 4.4K bytes - Viewed (0) -
docs/en/docs/tutorial/security/index.md
* This automatic discovery is what is defined in the OpenID Connect specification. /// tip Integrating other authentication/authorization providers like Google, Facebook, Twitter, GitHub, etc. is also possible and relatively easy. The most complex problem is building an authentication/authorization provider like those, but **FastAPI** gives you the tools to do it easily, while doing the heavy lifting for you. ///
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 4.3K bytes - Viewed (0) -
architecture/ambient/peer-authentication.md
of ztunnel is to be a minimal L4 proxy, and as such, its xDS configuration is purposefully limited. In particular, ztunnel only supports 2 (custom) xDS resources: [`Workload`](../../pkg/workloadapi/workload.proto) and [`Authorization`](../../pkg/workloadapi/security/authorization.proto). As such, ztunnel does not receive `PeerAuthentication`s directly; when istiod detects a `PeerAuthentication` resource that targets an Ambient captured workload, it computes the effective policy for that workload...
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Thu Aug 01 20:04:20 UTC 2024 - 3.9K bytes - Viewed (0) -
docs/em/docs/tutorial/security/first-steps.md
* 🕸 🏪 👈 🤝 🍕 👱. * 👩💻 🖊 🕸 🚶 ➕1️⃣ 📄 🕸 🕸 📱. * 🕸 💪 ☕ 🌅 💽 ⚪️➡️ 🛠️. * ✋️ ⚫️ 💪 🤝 👈 🎯 🔗. * , 🔓 ⏮️ 👆 🛠️, ⚫️ 📨 🎚 `Authorization` ⏮️ 💲 `Bearer ` ➕ 🤝. * 🚥 🤝 🔌 `foobar`, 🎚 `Authorization` 🎚 🔜: `Bearer foobar`. ## **FastAPI**'Ⓜ `OAuth2PasswordBearer` **FastAPI** 🚚 📚 🧰, 🎏 🎚 ⚛, 🛠️ 👫 💂♂ ⚒.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 6.8K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
* But it needs authentication for that specific endpoint. * So, to authenticate with our API, it sends a header `Authorization` with a value of `Bearer ` plus the token. * If the token contains `foobar`, the content of the `Authorization` header would be: `Bearer foobar`. ## **FastAPI**'s `OAuth2PasswordBearer`
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 9.2K bytes - Viewed (0) -
internal/config/lambda/target/webhook.go
return false, errNotConnected } return false, err } tokens := strings.Fields(target.args.AuthToken) switch len(tokens) { case 2: req.Header.Set("Authorization", target.args.AuthToken) case 1: req.Header.Set("Authorization", "Bearer "+target.args.AuthToken) } resp, err := target.httpClient.Do(req) if err != nil { if xnet.IsNetworkOrHostDown(err, true) { return false, errNotConnected
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Jul 08 21:39:49 UTC 2024 - 6.7K bytes - Viewed (0) -
internal/event/target/nats_contrib_test.go
opts := natsserver.DefaultTestOptions opts.Port = 14223 opts.Authorization = "s3cr3t" s := natsserver.RunServer(&opts) defer s.Shutdown() clientConfig := &NATSArgs{ Enable: true, Address: xnet.Host{ Name: "localhost", Port: (xnet.Port(opts.Port)), IsPortSet: true, }, Subject: "test", Token: opts.Authorization, } con, err := clientConfig.connectNats() if err != nil {
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri May 24 23:05:23 UTC 2024 - 2.3K bytes - Viewed (0) -
architecture/tests/integration.md
### Security Integration Tests - **Location**: `tests/integration/security` - **Purpose**: Tests related to the security features and components of Istio, such as authentication and authorization mechanisms. - **Focus**: 1. Authentication and authorization mechanisms. 1. Interaction between security components and Istio control plane. 1. Validation of mutual TLS (mTLS) configurations. 1. Testing of JWT token validation and RBAC policies.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Oct 09 00:57:44 UTC 2024 - 5.9K bytes - Viewed (0)