Lines Matching full:authentication

39 // authentication stack. A single instance of an HttpAuthController can be used
40 // to handle authentication to a single "target", where "target" is a HTTP
42 // of multiple authentication handlers (implemented as HttpAuthHandler
45 // Individual HTTP authentication schemes can have additional requirements other
52   // * |target| is either PROXY or SERVER and determines the authentication
59   //       3.3) of the URL is used by HTTP basic authentication to determine
70   //       authentication if explicit (user-provided) credentials are used and
71   //       they can be cached to respond to authentication challenges in the
73   //       authentication is stateful across requests. So the |http_auth_cache|
74   //       is also used to maintain state for this authentication scheme.
77   //       HttpAuthHandler subclasses to handle scheme-specific authentication
79   //       determining whether the authentication stack should use a specific
80   //       authentication scheme or not.
84   //       NTLM and Negotiate HTTP authentication schemes.
87   //       context allows ambient authentication using default credentials.
95   // Generate an authentication token for |target| if necessary. The return
123   // Return whether the authentication scheme is incompatible with HTTP/2
127   // Swaps the authentication challenge info into |other|.
168   // Invalidates any auth cache entries after authentication has failed.
172   // Allows reusing last used identity source. If the authentication handshake
196   // Holds the {scheme, host, port, path} for the authentication target.
199   // Holds the {scheme, host, port} for the authentication target.
202   // The absolute path of the resource needing authentication.
203   // For proxy authentication, the path is empty.
232   // in response to an HTTP authentication challenge.