Bug 1263336

Summary: [GSS](6.4.z) JACC Class can be specified as system properties but module can not be specified
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Darran Lofthouse <darran.lofthouse>
Component: SecurityAssignee: Brad Maxwell <bmaxwell>
Status: CLOSED CURRENTRELEASE QA Contact: Josef Cacek <jcacek>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.4.0CC: anmiller, bdawidow, bmaxwell, bspyrkos, cdewolf, cdolphy, darran.lofthouse, jawilson, olukas, pskopek, vtunka
Target Milestone: CR1   
Target Release: EAP 6.4.5   
Hardware: Unspecified   
OS: Unspecified   
URL: https://github.com/jbossas/jboss-eap/pull/2584
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1267355 (view as bug list) Environment:
Last Closed: 2017-01-17 11:36:59 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:
Bug Depends On:    
Bug Blocks: 1235745, 1267355    

Description Darran Lofthouse 2015-09-15 14:55:03 UTC 
Description of problem:

It is currently possible for JACC implementation classes to be specified as system properties, however it is not possible to specify the module to use when loading the classes.

This BZ is to correct this situation so a separate system property can also be set to control the module.
Comment 4 Ondrej Lukas 2015-11-04 13:09:28 UTC 
Verified in EAP 6.4.5.CP.CR1. Module for loading JACC policy can be specified through org.jboss.as.security.jacc-module system property.
Comment 5 Petr Penicka 2017-01-17 11:36:59 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.