Skip to content

DRIVERS-3181 fix timeouts in CSE custom endpoint test #1791

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 29, 2025
Merged

DRIVERS-3181 fix timeouts in CSE custom endpoint test #1791

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a0a937c
use "kmip" with bad port in CSE prose test 7 case 4
kevinAlbs Apr 28, 2025
05d7c28
use `.invalid` instead of `.local` for custom endpoint tests
kevinAlbs Apr 28, 2025
bbf4f0a
use `.invalid` in TLS options tests
kevinAlbs Apr 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 9 additions & 10 deletions source/client-side-encryption/tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -811,7 +811,7 @@ Configure with KMS providers as follows:
"endpoint": "doesnotexist.invalid:443"
},
"kmip": {
"endpoint": "doesnotexist.local:5698"
"endpoint": "doesnotexist.invalid:5698"
}
}
```
Expand Down Expand Up @@ -866,13 +866,12 @@ The method of passing TLS options for KMIP TLS connections is driver dependent.
Expect this to succeed. Use the returned UUID of the key to explicitly encrypt and decrypt the string "test" to
validate it works.

4. Call `client_encryption.createDataKey()` with "aws" as the provider and the following masterKey:
4. Call `client_encryption.createDataKey()` with "kmip" as the provider and the following masterKey:

```javascript
{
region: "us-east-1",
key: "arn:aws:kms:us-east-1:579766882180:key/89fcc2c4-08b0-4bd9-9f25-e30687b580d0",
endpoint: "kms.us-east-1.amazonaws.com:12345"
"keyId": "1",
"endpoint": "localhost:12345"
}
```

Expand Down Expand Up @@ -961,7 +960,7 @@ The method of passing TLS options for KMIP TLS connections is driver dependent.
validate it works.

Call `client_encryption_invalid.createDataKey()` with the same masterKey. Expect this to fail with a network
exception indicating failure to resolve "doesnotexist.local".
exception indicating failure to resolve "doesnotexist.invalid".

11. Call `client_encryption.createDataKey()` with "kmip" as the provider and the following masterKey:

Expand All @@ -980,11 +979,11 @@ The method of passing TLS options for KMIP TLS connections is driver dependent.
```javascript
{
"keyId": "1",
"endpoint": "doesnotexist.local:5698"
"endpoint": "doesnotexist.invalid:5698"
}
```

Expect this to fail with a network exception indicating failure to resolve "doesnotexist.local".
Expect this to fail with a network exception indicating failure to resolve "doesnotexist.invalid".

### 8. Bypass Spawning mongocryptd

Expand Down Expand Up @@ -1746,7 +1745,7 @@ Expect an error indicating TLS handshake failed due to an invalid hostname.
Call `client_encryption_no_client_cert.createDataKey()` with "azure" as the provider and the following masterKey:

```javascript
{ 'keyVaultEndpoint': 'doesnotexist.local', 'keyName': 'foo' }
{ 'keyVaultEndpoint': 'doesnotexist.invalid', 'keyName': 'foo' }
```

Expect an error indicating TLS handshake failed.
Expand Down Expand Up @@ -1858,7 +1857,7 @@ Call `client_encryption_with_names.createDataKey()` with "azure:no_client_cert"
masterKey:

```javascript
{ 'keyVaultEndpoint': 'doesnotexist.local', 'keyName': 'foo' }
{ 'keyVaultEndpoint': 'doesnotexist.invalid', 'keyName': 'foo' }
```

Expect an error indicating TLS handshake failed.
Expand Down
Loading