Bug 1263336 - [GSS](6.4.z) JACC Class can be specified as system properties but module can not be specified
Summary: [GSS](6.4.z) JACC Class can be specified as system properties but module can ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: CR1
: EAP 6.4.5
Assignee: Brad Maxwell
QA Contact: Josef Cacek
URL: https://github.com/jbossas/jboss-eap/...
Whiteboard:
Depends On:
Blocks: 1235745 1267355
TreeView+ depends on / blocked
 
Reported: 2015-09-15 14:55 UTC by Darran Lofthouse
Modified: 2019-10-10 10:12 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1267355 (view as bug list)
Environment:
Last Closed: 2017-01-17 11:36:59 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-5340 0 Major Closed Unable to specify module when specifying custom JACC policy class. 2019-06-03 08:41:12 UTC

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.


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