Home
last modified time | relevance | path

Searched refs:authentication (Results 1 – 25 of 1200) sorted by relevance

12345678910>>...48

/external/pigweed/pw_bluetooth_sapphire/host/gap/
Dtypes_test.cc33 BrEdrSecurityRequirements{.authentication = false, in TEST()
37 BrEdrSecurityRequirements{.authentication = false, in TEST()
41 BrEdrSecurityRequirements{.authentication = true, in TEST()
45 BrEdrSecurityRequirements{.authentication = true, in TEST()
53 BrEdrSecurityRequirements{.authentication = false, in TEST()
57 BrEdrSecurityRequirements{.authentication = false, in TEST()
61 BrEdrSecurityRequirements{.authentication = true, in TEST()
65 BrEdrSecurityRequirements{.authentication = true, in TEST()
72 BrEdrSecurityRequirements{.authentication = false, in TEST()
76 BrEdrSecurityRequirements{.authentication = false, in TEST()
[all …]
/external/curl/docs/libcurl/opts/
DCURLOPT_HTTPAUTH.md18 CURLOPT_HTTPAUTH - HTTP server authentication methods to try
31 authentication method(s) you want it to use speaking to the remote server.
34 first queries the host to see which authentication methods it supports and
40 For authentication with a proxy, see CURLOPT_PROXYAUTH(3).
44 HTTP Basic authentication. This is the default choice, and the only method
51 HTTP Digest authentication. Digest authentication is defined in RFC 2617 and
52 is a more secure way to do authentication over public networks than the
57 HTTP Digest authentication with an IE flavor. Digest authentication is defined
58 in RFC 2617 and is a more secure way to do authentication over public networks
65 HTTP Bearer token authentication, used primarily in OAuth 2.0 protocol.
[all …]
DCURLOPT_SOCKS5_AUTH.md17 CURLOPT_SOCKS5_AUTH - methods for SOCKS5 proxy authentication
30 authentication method(s) are allowed for SOCKS5 proxy authentication. The only
32 authentication, *CURLAUTH_GSSAPI*, which allows GSS-API authentication, and
33 *CURLAUTH_NONE*, which allows no authentication. Set the actual username and
54 /* enable username/password authentication only */
DCURLOPT_PROXY_TLSAUTH_TYPE.md22 CURLOPT_PROXY_TLSAUTH_TYPE - HTTPS proxy TLS authentication methods
36 the method of the TLS authentication used for the HTTPS connection. Supported
47 TLS-SRP authentication. Secure Remote Password authentication for TLS is
48 defined in RFC 5054 and provides mutual authentication if both sides have a
DCURLOPT_TLSAUTH_TYPE.md20 CURLOPT_TLSAUTH_TYPE - TLS authentication methods
33 the method of the TLS authentication. Supported method is "SRP".
43 TLS-SRP authentication. Secure Remote Password authentication for TLS is
44 defined in RFC 5054 and provides mutual authentication if both sides have a
DCURLOPT_USERNAME.md19 CURLOPT_USERNAME - username to use in authentication
36 authentication. You should not use this option together with the (older)
39 When using Kerberos V5 authentication with a Windows based server, you should
41 Kerberos Ticket. If you do not then the initial part of the authentication
52 authentication as well.
/external/okhttp/okhttp-tests/src/test/java/com/squareup/okhttp/internal/
DRecordingAuthenticator.java28 public final PasswordAuthentication authentication; field in RecordingAuthenticator
30 public RecordingAuthenticator(PasswordAuthentication authentication) { in RecordingAuthenticator() argument
31 this.authentication = authentication; in RecordingAuthenticator()
47 return authentication; in getPasswordAuthentication()
/external/googleapis/google/chat/v1/
Dchat_service.proto66 // [authentication](https://developers.google.com/workspace/chat/authenticate-authorize)
67 // and supports the following authentication types:
69 // - For text messages, user authentication or app authentication are
71 // - For card messages, only app authentication is supported. (Only Chat apps
85 // authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user).
97 // authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app)
102 // authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user)
106 // [authentication](https://developers.google.com/workspace/chat/authenticate-authorize).
109 // authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app)
111 // authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user).
[all …]
/external/grpc-grpc/examples/python/auth/
DREADME.md5 For most common usage of authentication in gRPC Python, please see our
29 This example focuses on extending gRPC authentication mechanism:
30 1) Customize authentication plugin;
36 Unlike TLS/SSL based authentication, the authentication extension in gRPC Python
41 gRPC Python provides a way to intercept an RPC and append authentication related
44 Those in need of a custom authentication method may simply provide a concrete
49 """A specification for custom authentication."""
52 """Implements authentication by passing metadata to a callback.
76 metadata_plugin: An AuthMetadataPlugin to use for authentication.
114 ## Token-based authentication
[all …]
/external/pigweed/pw_bluetooth_sapphire/host/gap/public/pw_bluetooth_sapphire/internal/host/gap/
Dtypes.h22 bool authentication; member
26 return authentication == rhs.authentication &&
32 .authentication = false, .secure_connections = false};
/external/grpc-grpc/doc/
Dserver_side_auth.md4 …ibes how server-side authentication works in C-core based gRPC implementations only. In gRPC Java …
9 …authentication, gRPC exposes the *authentication context* for each call. The context exposes impor…
11 The authentication context is structured as a multi-map of key-value pairs - the *auth properties*.…
13 …perty key will act as the peer identity (e.g. for client certificate authentication this property …
18 … to authenticating RPCs. Using any other call/context properties for authentication purposes is wr…
22 For secure channel using mutual TLS authentication with both client and server certificates (test c…
53 - TLS/SSL certificate authentication (built into gRPC's security layer, automatically used whenever…
54 - (coming soon) JWT auth token authentication
/external/openscreen/osp/msgs/
Dosp_messages.cddl46 authentication-request = {
48 1: authentication-mechanism ; mechanism
54 authentication-response = {
56 1: authentication-response-result ; result
61 authentication-result = {
62 1: authentication-result-result ; result
65 authentication-mechanism = &(
69 authentication-response-result = &(
80 authentication-result-result = &(
/external/curl/docs/cmdline-opts/
Dntlm.md5 Help: HTTP NTLM authentication
20 Use NTLM authentication. The NTLM authentication method was designed by
24 everyone who uses NTLM to switch to a public and documented authentication
27 If you want to enable NTLM for your proxy authentication, then use
Dsocks5-basic.md17 Use username/password authentication when connecting to a SOCKS5 proxy. The
18 username/password authentication is enabled by default. Use --socks5-gssapi to
19 force GSS-API authentication to SOCKS5 proxies.
Dproxy-basic.md5 Help: Use Basic authentication on the proxy
19 Use HTTP Basic authentication when communicating with the given proxy. Use
21 authentication method curl uses with proxies.
Dsocks5-gssapi.md17 Use GSS-API authentication when connecting to a SOCKS5 proxy. The GSS-API
18 authentication is enabled by default (if curl is compiled with GSS-API
19 support). Use --socks5-basic to force username/password authentication to
/external/googleapis/google/cloud/connectors/v1/
Dauthconfig.proto26 // AuthConfig defines details of a authentication type.
38 // Authorization Grant based authentication.
88 // The type of authentication configured.
110 // AuthConfigTemplate defines required field over an authentication type.
112 // The type of authentication configured.
118 // Display name for authentication template.
121 // Connector specific description for an authentication template.
125 // AuthType defines different authentication types.
134 // Authorization Grant based authentication
/external/googleapis/google/ads/searchads360/v0/errors/
Dauthentication_error.proto28 // Proto file describing authentication errors.
30 // Container for enum describing possible authentication errors.
32 // Enum describing possible authentication errors.
55 // A problem occurred during Google account authentication.
62 // Login cookie is required for authentication.
91 // An account administrator changed this account's authentication settings.
96 // An account administrator changed this account's authentication settings.
/external/googleapis/google/ads/googleads/v14/errors/
Dauthentication_error.proto28 // Proto file describing authentication errors.
30 // Container for enum describing possible authentication errors.
32 // Enum describing possible authentication errors.
55 // A problem occurred during Google account authentication.
62 // Login cookie is required for authentication.
89 // An account administrator changed this account's authentication settings.
94 // An account administrator changed this account's authentication settings.
/external/googleapis/google/ads/googleads/v15/errors/
Dauthentication_error.proto28 // Proto file describing authentication errors.
30 // Container for enum describing possible authentication errors.
32 // Enum describing possible authentication errors.
55 // A problem occurred during Google account authentication.
62 // Login cookie is required for authentication.
89 // An account administrator changed this account's authentication settings.
94 // An account administrator changed this account's authentication settings.
/external/trusty/arm-trusted-firmware/docs/design/
Dauth-framework.rst4 The aim of this document is to describe the authentication framework
62 This document describes the inner details of the authentication framework and
74 A CoT is basically a sequence of authentication images which usually starts with
125 Images in a CoT are categorised as authentication and data images. An
126 authentication image contains information to authenticate a data image or
127 another authentication image. A data image is usually a boot loader binary, but
128 it could be any other data that requires authentication.
144 #. If the image is an authentication image, extract the information that will
153 These components are responsible for initiating the authentication process for a
154 particular image in BL1 or BL2. For each BL image that requires authentication,
[all …]
/external/arm-trusted-firmware/docs/design/
Dauth-framework.rst4 The aim of this document is to describe the authentication framework
62 This document describes the inner details of the authentication framework and
74 A CoT is basically a sequence of authentication images which usually starts with
125 Images in a CoT are categorised as authentication and data images. An
126 authentication image contains information to authenticate a data image or
127 another authentication image. A data image is usually a boot loader binary, but
128 it could be any other data that requires authentication.
144 #. If the image is an authentication image, extract the information that will
153 These components are responsible for initiating the authentication process for a
154 particular image in BL1 or BL2. For each BL image that requires authentication,
[all …]
/external/wpa_supplicant_8/hostapd/
Dhlr_auc_gw.txt4 database/authentication gateway interface to HLR/AuC. It could be
6 authentication center (HLR/AuC). hostapd will send SIM/AKA
7 authentication queries over a UNIX domain socket to and external
10 hlr_auc_gw can be configured with GSM and UMTS authentication data with
13 dynamic authentication data for EAP-SIM, EAP-AKA, and EAP-AKA' while the
34 -g<triplet file> = path for GSM authentication triplets
79 authentication server for EAP-SIM/AKA/AKA':
/external/googleapis/google/ads/googleads/v16/errors/
Dauthentication_error.proto28 // Proto file describing authentication errors.
30 // Container for enum describing possible authentication errors.
32 // Enum describing possible authentication errors.
55 // A problem occurred during Google account authentication.
62 // Login cookie is required for authentication.
91 // An account administrator changed this account's authentication settings.
96 // An account administrator changed this account's authentication settings.
/external/autotest/server/cros/ap_configurators/
Dasus_qis_ap_configurator.py15 def _set_authentication(self, authentication, wait_for_xpath=None): argument
22 self.select_item_from_popup_by_xpath(authentication, auth,
135 def set_security_wep(self, key_value, authentication): argument
137 (key_value, authentication), 1, 1000)
140 def _set_security_wep(self, key_value, authentication): argument

12345678910>>...48