# Page History

## Key

• This line was removed.
• Formatting was changed.
Wiki Markup
Panel

JIRA

Client

1.x-2.x

*

,

and

connecting

to

Bugzilla

and

JIRA

servers

via

https://...

connections.

For

clarity,

this

article

is

written

JIRA

Client

and

JIRA,

but

it

applies

to

Deskzilla

/

Bugzilla

as

well.

### Problem

You need to use a client SSL certificate to connect to the server. In most cases, client certificate is not used. But in some high-security configurations it may be required.

When a connection is attempted to a server that requires a client certificate, it may result in the following error from JIRA Client:

Panel

Connection problem: Software caused connection abort: recv failed

JIRA Client does not have a direct way to specify a certificate. This article explains how to set up JIRA Client for using client certificate with standard Java tools.

Tip

The server certificate, which is used by the server to authenticate the connection, may be self-signed. In that case you will also need to apply the solution for self-signed server certificate.

### Solution

The solution is to create a secure file for storing your client certificate and specify it in command-line properties for JIRA Client.

#### 1. Obtain PKCS12 (.p12) file with the client certificate

You may already have it, but if you don't, it's easy to export the certificate from your browser. (We are assuming that you can access JIRA with your browser, hence the browser does have the certificate.)

Note

When specifying password for the exported certificate, enter at least 6 characters, and also without any space or special characters. Otherwise you may not be able to proceed later.

To export client certificate from Firefox, open Tools | Options menu, Advanced tab, and click on View Certificates. Select certificate that matches your server and click Backup button. Enter a file name for .p12 file, and then backup password. Remember backup password.

To export client certificate from Internet Explorer, open Tools | Internet Options dialog, Content tab, then click on Certificates button. Find your certificate and click Export. Follow the wizard. Include private key in export. Select PKCS 12 format (although the extension will be PFX, you can rename it to P12). Don't include extra options. Enter password and remember it.

As a result of this step, you should have .p12 file, let's call it my-certificate.p12 and the password for it.

#### 2. Create Java keystore using keytool

Use "keytool" program to transform the .p12 file. Keytool may be found in <JIRA Client Install Dir>\jre\bin (C:\Program Files\JIRA Client\jre\bin), or in any Java installation on your computer.

Run the following command:

Code Block
keytool -importkeystore -srckeystore c:\path\to\p12\my-certificate.p12 -srcstoretype pkcs12  -destkeystore c:\temporary\path\jiraclient.jks -deststoretype jks{code}



Substitute

...

path

...

to

...

the

...

exported

...

.p12

...

file

...

...

of

...

c:\path\to\p12\my-certificate.p12,

...

and

...

any

...

temporary

...

directory

...

...

of

...

c:\temporary\path.

...

Keytool

...

will

...

...

for

...

...

two

...

times

...

-

...

for

...

the

...

source

...

and

...

destination

...

keystores.

...

You

...

should

...

enter

...

the

...

...

you

...

created

...

on

...

the

...

previous

...

step

...

-

...

every

...

time.

...

It

...

will

...

be

...

the

...

same

...

...

for

...

both

...

key

...

stores.

...

Note

If passwords are different, it may result in the same errors on the client side and the following error in the server logs:

Code Block
SSL Library Error: 336105671 error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:
peer did not return a certificate No CAs known to server for verification?
{code}{note} As a result of this step, you should have file

As a result of this step, you should have file jiraclient.jks

...

in

...

a

...

temporary

...

directory.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

#### Copy ... jiraclient.jks ... from ... the ... previous ... step ... to ... C:\Program ... Files\JIRA ... Client, ... or ... whereever ... you ... have ... JIRA ... Client ... installed....To ... run ... JIRA ... Client ... with ... the ... client ... certificate, ... you ... will ... need ... to ... pass ... three ... additional ... parameters ... via ... command-line. ... To ... avoid ... typing ... them ... each ... time, ... you ... will ... need ... to ... modify ... the ... shortcut ... or ... script ... that ... you ... use ... to ... start ... JIRA ... Client....

...

...

##### On Linux

Modify "jiraclient.sh"

...

script.

...

Find

...

line

...

that

...

says

...

JAVA_OPTIONS="-Xmx600m

...

-Duse.metal=true"

...

.

...

Modify

...

it

...

so

...

it

...

says

...

}
Code Block
JAVA_OPTIONS="-Xmx600m -Duse.metal=true -Dforce.http.jre.executor=true -Djavax.net.ssl.keyStore=/path/to/jiraclient.jks -Djavax.net.ssl.keyStorePassword=<your password created at step 1>"
{code}



Note

...

the

...

quotes

...

are

...

around

...

all

...

the

...

line.

...

Use

...

full

...

path

...

to

...

specify

...

the

...

location

...

of

...

jiraclient.jks.

...

...

...

#### This is it!

Start JIRA Client. Try to connect. If it doesn't work, double-check that

• jiraclient.jks file exists and has at least 500 bytes;
• It is correctly pointed to using command-line properties;
• you really launch the same shortcut / script that you have edited.