After starting a Jive upgrade to version 9.4 from a version prior to 9.0.7, the following error is appearing for the "Update SAML Key Store Type" task in the Jive Upgrade Console:
- java.io.IOException: DER length more than 4 bytes: 78 at org.bouncycastle.asn1.ASN1InputStream.readLength(Unknown Source)
This issue is due to a change in the type of encryption provider that Jive uses in versions after 9.0.7. Versions later than 9.0.7 use the Bouncy Castle provider. To resolve this issue, it will be necessary to
Please follow these steps:
- Run the following query on your application database:
- select propvalue from jiveproperty where name = 'jive.storageprovider.FileStorageProvider.rootDirectory';
- Run the following command in your Jive binstore (replacing the placeholder <Jive binstore_path> with the query result from Step 1):
- find <Jive binstore_path>/jiveSBS -name "$(rev <<<saml46keystore)*" -o -name "*$(rev <<<saml46idp46metadata)*"
- If any files are found by the above command, move them to a folder that is outside of the Jive binstore.
- Run the following query in the application database:
- delete from jiveProperty WHERE name ilike '%saml%';
- Run the command jive restart on the server you are running the upgrade from.
- Return to the upgrade console.
- If the same error appears:
- Click on the Manual button that appears for the Update SAML Key Store Type task.
- Click on the Skip this Step button.
- Proceed with the remaining upgrade steps.
- Once the remaining steps are complete, a restart will be scheduled.
- After the restart, you will be directed to the Jive Setup Screen, where you will be prompted to complete the Encryption Key Management step.
- After completing that step, another restart will be scheduled.
- Once the restart is finished, you should be able to access the Jive admin console successfully.
Confirm you are using the upgraded version of Jive by:
- Browsing to the Admin Console > System.
- Check that the value of the Jive SBS Version field is 22.214.171.124.
If that version is not listed, or if you are unable to access the admin console after the upgrade, please contact us so that ATLAS can assist you. If you are not satisfied with the solution provided by ATLAS, then it will create a ticket for you on which you can attach the sbs.log files (located at /usr/local/jive/var/logs) from the server you started the upgrade.