From ecf18881b9456ed77e9d4be13a21bf207324d7b3 Mon Sep 17 00:00:00 2001 From: Stefan Kalscheuer Date: Thu, 23 Jun 2022 18:29:23 +0200 Subject: [PATCH] test: extend assertion for warnings creating token with custom ID With Vault 1.11 a second warning is raised. We accept "at least one" for now. --- .../de/stklcode/jvault/connector/HTTPVaultConnectorIT.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/test/java/de/stklcode/jvault/connector/HTTPVaultConnectorIT.java b/src/test/java/de/stklcode/jvault/connector/HTTPVaultConnectorIT.java index f6ed169..515de2c 100644 --- a/src/test/java/de/stklcode/jvault/connector/HTTPVaultConnectorIT.java +++ b/src/test/java/de/stklcode/jvault/connector/HTTPVaultConnectorIT.java @@ -908,7 +908,8 @@ class HTTPVaultConnectorIT { assertFalse(res.getAuth().isOrphan(), "Root token should not be orphan"); // Starting with Vault 1.0 a warning "custom ID uses weaker SHA1.." is given. - assertEquals(1, res.getWarnings().size(), "Token creation did not return expected warning"); + // Starting with Vault 1.11 a second warning "Endpoint ignored unrecognized parameters" is given. + assertFalse(res.getWarnings().isEmpty(), "Token creation did not return expected warning"); // Create token with attributes. Token token2 = Token.builder()