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

"Key sequence" always set to 00000 when saving uninitialised CA with available crypto token

    Details

    • Issue discovered during:
      Integration

      Description

      When a CA is imported from a statedump, it ends-up in uninitialised state. In this state, it is possible to make changes to the CA without having the crypto token available.

      If you modify the "Key sequence" for CA when crypto token is available, it will always be set to 00000, instead to the value you provided.

      If you modify the "Key sequence" for CA when crypto token is missing, the value will be set correctly (to whatever you specified).

      Reproduction steps:

      1. Import a CA via statedump. This CA will be referred to as "TestCA".

      2. Activate crypto token for TestCA.

      3. Open page "CA Functions" -> "Certification Authorities".

      4. Select "TestCA" from the list.

      5. Click on the "Edit CA" button.

      6. Set "Key sequence" to 11111.

      7. Click on the "Save" button.

      8. Select "TestCA" from the list again.

      9. Click on the "Edit CA" button.

      10. Check the value of "Key sequence"

      Expected results:

      1. Value for "Key sequence" is 00005.

      Actual results:

      1. Value for "Key sequence" is 00000.

      Additional details:

      As mentioned before, if the crypto token is missing, you can change the key sequence.

        Attachments

          Activity

            People

            Assignee:
            samuel Samuel Lidén Borell
            Reporter:
            branko Branko Majic (Inactive)
            Verified by:
            Tomas Gustavsson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: