Bug 1102257

Summary:	Installer: Vault validation on certain platforms is misleading
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Thomas Hauser <thauser>
Component:	Installer	Assignee:	Thomas Hauser <thauser>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tomas Livora <tlivora>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.2	CC:	kverlaen, mbaluch, rrajasek
Target Milestone:	CR1
Target Release:	6.0.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 19:51:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Thomas Hauser 2014-05-28 15:57:02 UTC

Description of problem:
The current version of the installer has checks that may erroneously indicate that certain keystores are valid when they are not.

Version-Release number of selected component (if applicable):
6.0.2 ER3

How reproducible:
Always

Steps to Reproduce:
1. Create a keystore with type PKCS12.
2. Use this keystore as the Vault keystore.

Actual results:
Validation passes (it should not pass here), and installation fails.

Expected results:
Validation does not allow the installation to proceed (Vault only supports JCEKS and JKS keystore types by default)

Additional info:
This issue affects BPMS and BRMS installers identically.

Comment 1 Thomas Hauser 2014-05-28 15:58:25 UTC

This issue is fixed in later versions of the installer code. Fixing it would just require a backport.

Comment 2 Marek Baluch 2014-06-19 08:49:16 UTC

Verified on 6.0.2.CR1.

When a keystore of type PKCS12 is provided the installer rejects it with message "This feature does not support the given keystore's type".