Details

    • Similar issues:
      KULRICE-10386Provide support for Bootstrap form classes
      KULRICE-11682Decide on provided help text
      KULRICE-8593Unsaved data want to leave dialog when clicking button to add a new KRMS proposition.
      KULRICE-11147Provide grid layout beans with Bootstrap table styles
      KULRICE-12240Analyze providing means of defining classes in KRAD DD files as Spring Beans
      KULRICE-12374Provide method to create disapproval note text in DocumentControllerBase
      KULRICE-2792SimpleWebServiceClientTest wants ThinClientResourceLoader to be first
      KULRICE-8164SOAPServiceTest.testWsdlGeneration integration test failing.
      KULRICE-13125Add quick fail tests for testing configuration changes
      KULRICE-2950Standalone Rice server fails to startup when log4j file is not present
    • Rice Team:
      QA
    • Rice Module:
      KSB

      Description

      testCertificatesExistInKeyStores fails with following trace (excerpted):

      java.lang.SecurityException: BC provider not installed!
      at org.bouncycastle.x509.X509V3CertificateGenerator.generateX509Certificate(Unknown Source)
      at org.kuali.rice.ksb.security.admin.service.impl.JavaSecurityManagementServiceImpl.generateCertificate(JavaSecurityManagementServiceImpl.java:204)
      at org.kuali.rice.ksb.security.admin.MockJavaSecurityManagementServiceImpl.setUpService(MockJavaSecurityManagementServiceImpl.java:56)
      at org.kuali.rice.ksb.security.admin.MockJavaSecurityManagementServiceImpl.getModuleKeyStore(MockJavaSecurityManagementServiceImpl.java:83)
      at org.kuali.rice.ksb.security.admin.service.impl.JavaSecurityManagementServiceImpl.isAliasInKeystore(JavaSecurityManagementServiceImpl.java:131)
      at org.kuali.rice.ksb.security.admin.service.impl.JavaSecurityManagementServiceImpl.generateClientKeystore(JavaSecurityManagementServiceImpl.java:139)
      at org.kuali.rice.ksb.security.admin.JavaSecurityManagementServiceTest.testCertificatesExistInKeyStores(JavaSecurityManagementServiceTest.java:50)
      ....

      This is a common error and indicates that the BouncyCastle provider has not been registered with the JCE (either staticallly, in the java.security file of the JRE, or dynamically).

      I can resolve this issue locally by editing the JRE's java.security file, but that does not seem like the best solution.

        Activity

        Hide
        Casey Boettcher (Inactive) added a comment -

        Added this to unit test:

        //test that Bouncy Castle provider is present and add it if it's not
        if( Security.getProvider(BouncyCastleProvider.PROVIDER_NAME) == null)

        { Security.addProvider(new BouncyCastleProvider()); }

        A couple of things we might want to consider:
        1) implementor should be able to set provider via Spring
        2) use most recent version of jkd1.5 provider from BC rathern than 133 (they're up to 142 now)
        3) the call to add a provider should be made during setup of the SecurityManagementService, no?

        Show
        Casey Boettcher (Inactive) added a comment - Added this to unit test: //test that Bouncy Castle provider is present and add it if it's not if( Security.getProvider(BouncyCastleProvider.PROVIDER_NAME) == null) { Security.addProvider(new BouncyCastleProvider()); } A couple of things we might want to consider: 1) implementor should be able to set provider via Spring 2) use most recent version of jkd1.5 provider from BC rathern than 133 (they're up to 142 now) 3) the call to add a provider should be made during setup of the SecurityManagementService, no?

          People

          • Assignee:
            Casey Boettcher (Inactive)
            Reporter:
            Casey Boettcher (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel