Lines Matching +full:auth +full:- +full:tests
6 and the [gRPC over HTTP/2 v2 protocol](./PROTOCOL-HTTP2.md).
9 ------
12 provided the test case it is expected to run as a command-line parameter. Names
16 * --server_host=HOSTNAME
18 * --server_host_override=HOSTNAME
20 :authority header. If unspecified, the value of --server_host will be
22 * --server_port=PORT
24 * --test_case=TESTCASE
26 * --use_tls=BOOLEAN
28 * --use_test_ca=BOOLEAN
32 * --default_service_account=ACCOUNT_EMAIL
34 * --oauth_scope=SCOPE
35 * OAuth scope. For example, "https://www.googleapis.com/auth/xapi.zoo"
36 * --service_account_key_file=PATH
39 * --service_config_json=SERVICE_CONFIG_JSON
42 * --additional_metadata=ADDITIONAL_METADATA
43 * Additional metadata to send in each request, as a semicolon-separated list
46 next semi-colon thereafter, and so on. For example:
47 - `abc-key:abc-value;foo-key:foo-value`
48 - Key/value pairs: `abc-key`/`abc-value`, `foo-key`/`foo-value`.
49 - `abc-key:abc:value;foo-key:foo:value`
50 - Key/value pairs: `abc-key`/`abc:value`, `foo-key`/`foo:value`.
52 Keys must be ASCII only (no `-bin` headers allowed). Values may contain
53 any character except semi-colons.
60 This test verifies that implementations support zero-size messages. Ideally,
73 * response is non-null
84 cache matches left over from previous tests.
93 Client adds a `x-user-ip` header with value `1.2.3.4` to the request.
248 This test verifies that client-only streaming succeeds.
295 6. Client half-closes
304 This test verifies the client can compress requests on per-message basis by
305 performing a two-request streaming call. It also sends an initial probing
310 1. Client calls `StreamingInputCall` and sends the following feature-probing
351 1. Client half-closes
361 This test verifies that server-only streaming succeeds.
500 5. After getting a reply, client half-closes
511 This test verifies that streams support having zero-messages in both
518 1. Client calls FullDuplexCall and then half-closes
526 This test is only for cloud-to-prod path.
532 The test uses `--default_service_account` with GCE service account email and
533 `--oauth_scope` with the OAuth scope to use. For testing against
534 grpc-test.sandbox.googleapis.com, "https://www.googleapis.com/auth/xapi.zoo"
536 be passed in as `--oauth_scope`.
561 `--default_service_account` flag
562 * received SimpleResponse.oauth_scope is in `--oauth_scope`
569 This test is only for cloud-to-prod path.
574 Test caller should set flag `--service_account_key_file` with the
577 usable auth implementation, she may specify the file location in the environment
602 by the auth library. The client can optionally check the username matches the
603 email address in the key file or equals the value of `--default_service_account`
611 This test is only for cloud-to-prod path and some implementations may run
617 language-specific authorization library.
619 The difference between this test and the other auth tests is that it
623 - uses the flag `--service_account_key_file` with the path to a json key file
625 usable auth implementation, it may specify the file location in the environment
627 fetch the token, `--default_service_account` can be used to pass in GCE service
629 - uses the flag `--oauth_scope` for the oauth scope. For testing against
630 grpc-test.sandbox.googleapis.com, "https://www.googleapis.com/auth/xapi.zoo"
631 should be passed as the `--oauth_scope`.
639 1. Client uses the auth library to obtain an authorization token
656 * received SimpleResponse.oauth_scope is in `--oauth_scope`
660 Similar to the other auth tests, this test is only for cloud-to-prod path.
666 - uses the flag `--service_account_key_file` with the path to a json key file
668 usable auth implementation, it may specify the file location in the environment
670 - optionally uses the flag `--oauth_scope` for the oauth scope if implementer
672 against grpc-test.sandbox.googleapis.com, oauth scope
673 "https://www.googleapis.com/auth/xapi.zoo" should be used.
682 2. Client calls UnaryCall, setting per-call credentials to
694 by the auth library. The client can optionally check the username matches the
699 Similar to the other auth tests, this test should only be run against prod
700 servers. Different from some of the other auth tests however, this test
709 The test uses `--default_service_account` with GCE service account email.
720 is capable of transport creds auto-selection (including ALTS).
721 Similar APIs involving only auto-selection of OAuth mechanisms
734 `--default_service_account`
738 Similar to the other auth tests, this test should only be run against prod
745 The test uses `--default_service_account` with GCE service account email. This
758 is capable of transport creds auto-selection (including ALTS).
771 `--default_service_account`
776 sent as initial-metadata by the client and as both initial- and trailing-metadata
788 key: "x-grpc-test-echo-initial", value: "test_initial_metadata_value"
789 key: "x-grpc-test-echo-trailing-bin", value: 0xababab
806 key: "x-grpc-test-echo-initial", value: "test_initial_metadata_value"
807 key: "x-grpc-test-echo-trailing-bin", value: 0xababab
823 and then half-closes
827 * metadata with key `"x-grpc-test-echo-initial"` and value
830 * metadata with key `"x-grpc-test-echo-trailing-bin"` and value `0xababab` is
868 and then half-closes
893 message: "\t\ntest with whitespace\r\nand Unicode BMP ☺ and non-BMP ��\t\n"
1017 b) the sum of RPCs that either completed with a non-OK status or exceeded
1020 Implementations should use a timer with sub-millisecond precision to measure
1031 - Upon success:
1032 - `soak iteration: \d+ elapsed_ms: \d+ peer: \S+ succeeded`
1034 - Upon failure:
1035 - `soak iteration: \d+ elapsed_ms: \d+ peer: \S+ failed:`
1044 still exit 0). A failure is considered to be either a non-OK status or an RPC
1086 will receive per-query metric reports from the backend.
1090 per-query report listener. The interop-testing client will run with a service
1092 `--service_config_json`), so that it effectively uses this newly registered
1126 * The per-query load report reference contains a metrics report that is
1132 will receive out-of-band metric reports from the backend.
1137 out-of-band report listener (configure load report interval to be 1s) in the LB
1138 policy. The interop-testing client will run with a service config to select the
1139 load balancing config(using argument `--service_config_json`), so that it
1193 ### Experimental Tests
1195 These tests are not yet standardized, and are not yet implemented in all
1200 The client performs a number of large_unary RPCs over a single long-lived
1207 Client performs 1000 large_unary tests in parallel on the same channel.
1216 ### TODO Tests
1259 ### Postponed Tests
1261 Resilience to buggy servers: These tests would verify that a client application
1273 ------
1282 * --port=PORT
1286 * --use_tls=BOOLEAN
1318 to pass. Currently we set the max-age to 60 seconds.
1362 [Echo Status]: #echo-status
1367 associated status messages end-to-end.
1370 [Echo Metadata]: #echo-metadata
1371 When the client sends metadata with the key `"x-grpc-test-echo-initial"` with its
1374 `"x-grpc-test-echo-trailing-bin"` with its request, the server sends back exactly this
1378 [Observe ResponseParameters.interval_us]: #observe-responseparametersinterval_us
1388 ### Echo Auth Information
1393 [Echo Authenticated Username]: #echo-authenticated-username
1402 [Echo OAuth Scope]: #echo-oauth-scope
1408 Although a general server-side feature, most test servers won't implement this
1409 feature. The TLS server `grpc-test.sandbox.googleapis.com:443` supports this
1411 `https://www.googleapis.com/auth/xapi.zoo` for authentication to succeed.
1420 [Backend Metrics Report]: #backend-metrics-report
1422 Server reports backend metrics data in both per-query and out-of-band cases,
1425 Using ORCA APIs we install the per-query metrics reporting server interceptor,
1438 one client to control the server's out-of-band reports until the end of the RPC.