Kantega SSO code signing certificate

In newer versions of Atlassian’s data center offerings, the universal plugin manager (UPM) has app signature verification enabled by default. When installing our app directly from the marketplace, you may set up Atlassian’s signature settings following their instructions:

Installing a custom build sent by Kantega SSO

Sometimes during troubleshooting or support, you may receive a custom build from Kantega SSO. In order to install that in an environment that has signature checks enabled, you will need to configure trust towards Kantega SSO’s signing certificate and use the signature signed by us.

The signing certificate (kantega-sso-app-signature-root-ca.crt) can be downloaded from https://ca.kantega-sso.com. Install it into the truststore that lies under upmconfig in the home directory of the data center installation. Then download the key and provide it to UPM during the jar file upload.

The signature will be provided through an URL together with the jar artifact, usually like this:

Jar file URL:

https://files.kantega-sso.com/kerberosauth-plugin-8.1.1.p7-20250915.000930-22-jira10.jar

Signature URL:

https://files.kantega-sso.com/kerberosauth-plugin-8.1.1.p7-20250915.000930-22-jira10.jar.pem

Downgrading to a version outside marketplace

Signatures are always bundled with jar files when Kantega SSO Enterprise is released. https://packages.kantega-sso.com contains signatures for all files. See for example https://packages.kantega-sso.com/no/kantega/kerberosauth/kerberosauth-plugin/8.1.1.p6/: