github/infisical
1
0
Fork 0
mirror of https://github.com/Infisical/infisical.git synced 2026-01-08 23:18:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

Allow empty CN

Browse Source
This commit is contained in:
Fang-Pen Lin
2025-11-20 16:56:18 -08:00
parent 02c346c77a
commit cf83ae2553
7 changed files with 23 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
backend/bdd/features/pki/acme/internal-ca.feature
View File

@@ -1,13 +1,13 @@
Feature: Internal CA
Scenario Outline: CSR with SANs only
Scenario: CSR with SANs only
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 "{acme_profile.eab_kid}" with secret "{acme_profile.eab_secret}" as acme_account
When I create certificate signing request as csr
Then I add names to certificate signing request csr
"""
<names>
{}
"""
And I add subject alternative name to certificate signing request csr
"""
@@ -25,8 +25,3 @@ Feature: Internal CA
And the value finalized_order.body with jq ".status" should be equal to "valid"
And I parse the full-chain certificate from order finalized_order as cert
And the value cert with jq ".subject.common_name" should be equal to "localhost"
Examples:
| names |
| {} |
| {"COMMON_NAME": ""}