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

Trying to save P11 crypto token with incorrect PIN makes EJBCA think token already exists

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: EJBCA 7.0.0
    • Fix Version/s: EJBCA 7.0.1
    • Component/s: CA GUI
    • Labels:
    • Issue discovered during:
      Testing
    • Sprint:
      EJBCA Team Alice - 2019 w6

      Description

      Steps to reproduce:

      1. Go to Crypto Tokens -> Create new...
      2. Select Type PKCS#11 and enter PKCS#11 reference information to a slot that has not previously been added
      3. Enter and repeat an incorrect authentication code (token PIN) and click save
      4. Expected error message is shown: Error: Failed to initialize PKCS11 provider slot ... 
      5. Enter correct authentication code (token PIN) and click save
      6. Error message is shown saying that the token already exists 
      • The P11 slot is already used by other crypto token(s); SunPKCS11-libsofthsm2.so-slot3 (database protection?). Re-using P11 slots in multiple crypto tokens is discouraged, and all parameters must be identical. Re-enter authentication code and Confirm Save to continue.
         

      Obvious workaround exists, enter correct code again and clicking "confirm save".

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tomas Tomas Gustavsson
                Reporter:
                Hodell Anton Hodell
                Verified by:
                Henrik Sunmark
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 hour Original Estimate - 1 hour
                  1h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour, 15 minutes
                  1h 15m