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

EJBCA 7.3.0 and ACME with cleartextpassword

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: EJBCA 7.3.0
    • Fix Version/s: EJBCA 7.3.1, EJBCA 7.3.0.1
    • Component/s: Protocols
    • Labels:
      None
    • Environment:
      AWS Linux 2, but this will happen in all cases. This is with EJBCA 7.3.0 and Certbot 0.31.
    • Issue discovered during:
      Ad Hoc
    • Sprint:
      EJBCA Team Alice - 2019 w40, EJBCA Team Alice - 2019 w42

      Description

      Using Certbot 0.31 with EJBCA 7.3.0 has a bug with regards to clear text password and batch processing.  I have spoken to Tomas Gustavsson and he said this has happened with other protocols in the past.  When enrolling with ACME, the error gets generated:

       

      An unexpected error occurred:
      The CSR is unacceptable (e.g., due to a short key) :: Clearpassword (used in batch processing) cannot be used.

      There are two problems with this.  One is that Tomas said: "We've had similar issues with other protocols, a flag in the code that is set wrongly when creating an end entity."

       

      The second is that this is the error that gets generated when the batch box is not checked.  Its a bit misleading because the box is not checked, and its telling me it cannot be used.  Which its not.  Fixing problem #1 may solve this problem, but if the error will be triggered still it should read something more that aligns with its usage.  As it stands now, the error seems to read the opposite of what is happening in the EE profile.

        Attachments

          Activity

            People

            Assignee:
            tomas Tomas Gustavsson
            Reporter:
            alex.gregory@primekey.com Alex Gregory
            Verified by:
            Amin Khorsandi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 30 minutes
                30m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 30 minutes
                30m