Bug 1108310 - [GSS] (6.4.0) Improve the ability to use MS Windows keystore for the web servers ssl connector
Summary: [GSS] (6.4.0) Improve the ability to use MS Windows keystore for the web serv...
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: EAP 6.4.0
Assignee: Rémy Maucherat
QA Contact: Jan Stefl
Russell Dickenson
Depends On: 1138672
Blocks: 1108307
TreeView+ depends on / blocked
Reported: 2014-06-11 17:06 UTC by Derek Horton
Modified: 2018-12-05 18:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1108307
Last Closed: 2017-02-26 04:52:35 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3483 0 Major Closed Improve the ability to use MS Windows keystore for the web servers ssl connector 2019-09-29 22:21:27 UTC

Description Derek Horton 2014-06-11 17:06:50 UTC
+++ This bug was initially created as a clone of Bug #1108307 +++

Description of problem:
It is possible to configure the web ssl connector to use the Windows certificate keystore (access provided by the SunMSCAPI provider). However, the JSSESocketFactory checks for a keystore file. This check should likely be skipped when the connector is configured to use the Windows keystore.

Here is what the configuration looks like:
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl name="https" 

This results in an error like this:
13:54:01,821 ERROR [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003043: Error initializing endpoint: java.io.FileNotFoundException: C:\Users\imauser\.keystore (The system cannot find the file specified)

You can work around this issue by creating this keystore (C:\Users\imauser\.keystore).

More info on using the Windows keystores can be found here:

Comment 1 JBoss JIRA Server 2014-06-18 16:11:18 UTC
Emmanuel Hugonnet <ehugonne> updated the status of jira WFLY-3483 to Resolved

Comment 6 Mike McCune 2016-03-28 23:29:09 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Note You need to log in before you can comment on or make changes to this bug.