awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-08 14:28:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

More test cases

Browse Source
This commit is contained in:
Fang-Pen Lin
2025-11-12 09:12:12 -08:00
parent 9e12d67e01
commit 3246b80c81
2 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/bdd/features/pki/acme/account.feature
+13
View File
@@ -11,3 +11,16 @@ Feature: Account
When I have an ACME client connecting to {BASE_URL}/api/v1/pki/acme/profiles/{acme_profile.id}/directory
Then I register a new ACME account with email fangpen@infisical.com without EAB
Then the value error with jq ".type" should be equal to "urn:ietf:params:acme:error:externalAccountRequired"
Scenario Outline: Scenario: Create a new account with bad EAB credentials
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
Then I register a new ACME account with email fangpen@infisical.com and EAB key id "<eab_kid>" with secret "<eab_secret>" as acme_account
Then the value error with jq ".type" should be equal to "urn:ietf:params:acme:error:malformed"
Then the value error with jq ".detail" should be equal to "Invalid external account binding JWS signature"
Examples: Bad Credentials
| eab_kid | eab_secret |
| bad | Cg== |
| {acme_profile.eab_kid} | Cg== |
| 4bc7959c-fe2d-4447-ae91-0cd893667af6 | {acme_profile.eab_secret} |