Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1051057

Summary: LdapExtLoginModule's bindCredential requires vault string to be in a slightly different format than other components
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Derek Horton <dehort>
Component: SecurityAssignee: Anil Saldhana <anil.saldhana>
Status: CLOSED CURRENTRELEASE QA Contact: Josef Cacek <jcacek>
Severity: high Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0   
Target Milestone: GA   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-30 06:45:40 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:
Attachments:
Description Flags
potential fix none

Description Derek Horton 2014-01-09 16:17:06 UTC
Description of problem:

The LdapExtLoginModule requires that the vault string used for the bindCredentials not include the '${' prefix and '}' suffix. This is different than other places in the standalone.xml file where the ${ and } are required.

Comment 1 Derek Horton 2014-01-09 16:17:59 UTC
Created attachment 847718 [details]
potential fix

Comment 2 Josef Cacek 2014-07-30 06:45:40 UTC
This issue reported against older version, cannot be reproduced against latest 6.3.0. bits, which means it was fixed earlier. Therefore, we are closing this bug. Thank you for reporting this issue. 

The behavior of SecurityVaultUtil.isVaultFormat() method has not changed, but it seems login modules get already decrypted module options now.

I'm leaving open the related JIRA SECURITY-783.