Bug 972543 - JaasSecurityDomain is missing in EAP6
Summary: JaasSecurityDomain is missing in EAP6
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: EAP 6.3.0
Assignee: Peter Skopek
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-10 01:40 UTC by Hisanobu Okuda
Modified: 2019-08-19 12:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:48:34 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)

Description Hisanobu Okuda 2013-06-10 01:40:34 UTC
Description of problem:
JaasSecurityDomain is one of features which EAP5 has and is missing from EAP6. Some of our EAP5 customers don't like to move to the password vault, because they don't want to manage keystores for their thousands of VMs. Please reinstate JaasSecurityDomain or an alternative implementation which has a similar usability of JaasSecurityDomain.

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

EAP 6.x

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Anil Saldhana 2013-06-11 17:23:05 UTC
Have you looked at <jsse> element of the security subsystem configuration?
https://docs.jboss.org/author/display/AS7/Security+subsystem+configuration

Comment 4 Hisanobu Okuda 2013-06-12 01:41:25 UTC
Thanks for the suggestion, Anil. The customer wants to encrypt passwords for various data sources and user stores for authentication independently and not storing them in a keystore. Please see Comment #1.

Comment 6 Hisanobu Okuda 2013-07-19 08:29:17 UTC
Requesting this for inclusion to 6.2

Comment 7 Hisanobu Okuda 2013-11-08 02:37:24 UTC
Request for inclusion to EAP 6.3.0

Comment 10 Stefan Guilhen 2014-02-25 14:53:15 UTC
Assigning to Peter for evaluation


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