Uploaded image for project: 'EJBCA'
  1. EJBCA
  2. ECA-7206

End Entity Profile setting to allow dnsName SAN field to be automatically populated by the CN in a CSR

        Details

        • Type: New Feature
        • Status: Closed
        • Priority: Critical
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: EJBCA 7.0.1
        • Component/s: None
        • Labels:
          None
        • Provenance:
          Internal Delivery
        • Issue discovered during:
          Customer
        • Epic Link:
        • Sprint:
          EJBCA Team Bob - 2019 w6

          Description

          We're getting the same feature request more and more often, to be able to automatically set the dnsName based on the the CN. 

          I would suggest implementing this as a check box in the EEP (in the SAN level), which if activated would automatically create a dnsName SAN field in the EE based on the CN. 

           

            Attachments

              Issue Links

              causes

              Bug - A problem which impairs or prevents the functions of the product. ECA-7972 CN is not copied to dNSName when "Use entity CN field" is enabled in the end entity profile

              • Major - Major loss of function.
              • Open
              is related to

              Improvement - An improvement or enhancement to an existing feature or task. ECA-7884 System test for copying DNSName from CN over WS

              • Minor - Minor loss of function, or other problem where easy workaround is present.
              • Closed

                Activity

                  People

                  • Assignee:
                    katja_helmes Jekaterina Bunina
                    Reporter:
                    mikek Mike Agrenius Kushner
                    Verified by:
                    Samuel Lidén Borell
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    6 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved:

                      Time Tracking

                      Estimated:
                      Original Estimate - 4 days Original Estimate - 4 days
                      4d
                      Remaining:
                      Remaining Estimate - 0 minutes
                      0m
                      Logged:
                      Time Spent - 1 week, 1 day
                      1w 1d