[jboss-jira] [JBoss JIRA] (WFLY-7808) Security subsystem, audit provider-module lacks "module" attribute
Peter Palaga (JIRA)
issues at jboss.org
Tue Jan 3 10:44:00 EST 2017
[ https://issues.jboss.org/browse/WFLY-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13342659#comment-13342659 ]
Peter Palaga commented on WFLY-7808:
------------------------------------
I'll turn this branch https://github.com/ppalaga/wildfly/commits/WFLY-7808 into a PR once https://github.com/wildfly/wildfly/pull/9508 gets merged.
> Security subsystem, audit provider-module lacks "module" attribute
> ------------------------------------------------------------------
>
> Key: WFLY-7808
> URL: https://issues.jboss.org/browse/WFLY-7808
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Time Spent: 6 hours
> Remaining Estimate: 0 minutes
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1392436 :
> When adding a provider module for auditing:
> {code}
> [standalone at orac.usersys.redhat.com:9999 /] /subsystem=security/security-domain=LdapRealm/audit=classic/provider-module=test:add(
> => hit TAB
> code= module-options=
> {code}
> There is no attribute "module" which would allow a customer to install a custom module.
> Workaround: custom jar file must be added to the "org.picketbox" module.
> However, this needs to be checked/redone each time a CP is installed making it a big overhead when a customer has many installations.
> Logging as a bug and not an RFE, as the presence of the "module" attribute was expected.
> The "module" attribute is defined in the jboss-as-security and wildfly-security schemas since version 1.1, but it seems to never have been implemented.
> cc [~tfonteyn], [~j_ri]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list