Bug 904113 - Step 5 of Procedure 19.1. fails
Summary: Step 5 of Procedure 19.1. fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 5
Classification: JBoss
Component: doc-JBoss_Security_Guide
Version: 5.2.0,5.1.2
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Scott Mumford
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-25 13:38 UTC by Ivo Studensky
Modified: 2015-04-24 00:55 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-04-24 00:55:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ivo Studensky 2013-01-25 13:38:00 UTC
Description of problem:
In the Procedure 19.1. of the Security Guide the Step 5 does not work. It is not possible to pass a plain-text version of the password to the encode64(String password) simply because the encode64 method of the JaasSecurityDomainMBean class has a signature 'encode64(byte[] secret)' instead of 'encode64(String password)'. So in order to get an encrypted password it is needed to pass a comma/space-separated list of bytes corresponding to the password.

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

How reproducible:
Follow instructions in the Procedure 19.1.

Additional info:
It is not hard to produce a comma-separated list of a String in Java, but it needs a programmer intervention which IMO is not acceptable for a documented and thus recommended procedure. I would prefer to add an encode64 method to JaasSecurityDomainMBean that can accept the password in String.

Comment 1 Ivo Studensky 2013-01-25 14:33:57 UTC
Created a jira for tracking the issue in the product code, see

https://issues.jboss.org/browse/JBPAPP-10607

Comment 2 Usman Saleem 2013-04-15 23:47:49 UTC
A workaround is to use PBEUtils to encode password:

java -cp ./lib/jbosssx.jar org.jboss.security.plugins.PBEUtils 8-char-salt iteration_count keystorepassword plain_bind_password


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