Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1058469 - Installer: missing strings
Summary: Installer: missing strings
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Installer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER2
: 6.1.0
Assignee: trev
QA Contact: Len DiMaggio
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-27 20:52 UTC by Thomas Hauser
Modified: 2016-02-10 08:56 UTC (History)
4 users (show)

Doc Type: Release Note
Doc Text:
When configuring JSSE using the JBoss Data Virtualization installer, some of the error messages displayed are incorrect. If the user enters a location that is not accessible to the installer in the JSSE keystore/truststore location fields, the error message currently reads "securitydomain.jsse.keystore.inaccessible". It should read "The location given for the truststore either doesn't exist or is inaccessible at this time. Continue?". Similarly, if the user enters a password that is incorrect for the given keystore (if it is of type JKS), or if the keystore is not of type JKS, the error message currently reads "securitydomain.jsse.keystore.passincorrect". It should read "The password for the truststore was incorrect, or the keystore is not of type JKS. Continue?" Both of these errors can be ignored if the user is confident of the information provided.
Clone Of:
Last Closed: 2016-02-10 08:56:37 UTC
Type: Bug

Attachments (Terms of Use)

Description Thomas Hauser 2014-01-27 20:52:09 UTC
Description of problem:
There are missing strings in the JSSE window.

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

How reproducible:

Steps to Reproduce:
1. Navigate to the JSSE configuration panel.
2. Choose to add a keystore.
3. In the keystore URL field, add an non-existing location.
1. Same as above.
2. Same as above. 
3. In the keystore password fields, enter an incorrect password to the keystore indicated in the keystore URL field.

Actual results:
The user is displayed
in scenario a), or
in scenario b).

In either case, the option to continue the installation anyway is offered, because the checks for these fields do not exhaust all possible keystore types (for the password check) or all protocols where a keystore could exist.

This issue is also mirrored to the truststore url / password fields.

Comment 2 Ahmed Abu Lawi 2014-07-23 14:05:49 UTC
The langpacks have been updated to provide the correct warning messages.

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