[
https://issues.jboss.org/browse/WFLY-5227?page=com.atlassian.jira.plugin....
]
Ken Wills commented on WFLY-5227:
---------------------------------
Updated, working core diff here, with GAV change and a manual fixup of the metadata dep
removal and additional loggers added previously:
https://github.com/wildfly/wildfly-core/compare/master...luck3y:security-...
As part of some rebase weirdness, removing commits up to 'de72c28 WFLY-401 Add the
security manager subsystem' leaves some legacy code around (Security actions). I could
either continue with the truncated rebase and manually remove these files at the end, or
just include the complete history. I think it makes sense to go with the complete
histrory.
Core boots and works, both with and without -secmgr, though I don't know how to test
it further than that :)
Move security-manager subsystem from WildFly to WildFly Core
------------------------------------------------------------
Key: WFLY-5227
URL:
https://issues.jboss.org/browse/WFLY-5227
Project: WildFly
Issue Type: Bug
Components: Security Manager
Reporter: Josef Cacek
Assignee: Ken Wills
Priority: Critical
It's not possible to define security permissions in WildFly Core without
{{security-manager}} subsystem. Therefore the subsystem should be moved from WildFly to
the Core.
More details in the [Permissions in WildFly
Core|http://lists.jboss.org/pipermail/wildfly-dev/2015-August/thread.html...] thread on
{{wildfly-dev}} mailing list.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)