From 173eb48763c072c0c118e74268f60a0daeb06419 Mon Sep 17 00:00:00 2001 From: Fang-Pen Lin Date: Thu, 6 Nov 2025 19:27:38 -0800 Subject: [PATCH] Add more corner cases --- backend/bdd/features/pki/acme/account.feature | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/backend/bdd/features/pki/acme/account.feature b/backend/bdd/features/pki/acme/account.feature index c10d93d9d..4df675669 100644 --- a/backend/bdd/features/pki/acme/account.feature +++ b/backend/bdd/features/pki/acme/account.feature @@ -32,13 +32,15 @@ Feature: Account Given I have an ACME cert profile as "acme_profile" When I have an ACME client connecting to {BASE_URL}/api/v1/pki/acme/profiles/{acme_profile.id}/directory When I use a different new-account URL "" for EAB signature - Then I register a new ACME account with email fangpen@infisical.com and EAB key id "" with secret "" as acme_account + Then I register a new ACME account with email fangpen@infisical.com and EAB key id "{acme_profile.eab_kid}" with secret "{acme_profile.eab_secret}" as acme_account Then the value error with jq ".type" should be equal to "urn:ietf:params:acme:error:externalAccountRequired" Then the value error with jq ".detail" should be equal to "External account binding URL mismatch" Examples: Bad URLs | url | | {BASE_URL}/api/v1/pki/acme/profiles/{acme_profile.id}/new-account-bad | + | {BASE_URL}/api/v1/pki/acme/profiles/{acme_profile.id}/new-account?foo=bar | + | {BASE_URL}/api/v1/pki/acme/profiles/{acme_profile.id}/new-account#foobar | | {BASE_URL}/acme/new-account | | https://example.com/api/v1/pki/acme/profiles/{acme_profile.id}/new-account-bad | | bad |