Security manager and security permissions features:
- security manager subsystem that installs the WildFlySecurityManager
and allows specification of seurity permissions that are to be applied
to all deployments;
- parsing of META-INF/permissions.xml as per spec: subdeployments cannot
define their own permissions. Instead they can only inherit permissions
(if any) from the parent EAR;
- parsing of META-INF/jboss-permissions.xml: WF-specific descriptor that
allows subdeployments to define their own set of permissions regardless
of those declared at the EAR level;
- jboss modules also allow for the configuration of permissions in
module.xml;
- more efficient usage of privileged blocks: they are only used if the
WildFlySecurityManager is active.
That's what I remember right now
Stefan
On 02/11/2014 12:38 PM, Jason Greene wrote:
Hi Everyone,
I am working on the release notes. In order to save time I thought I would try something
new, and just ask that you email me a blurb covering anything important you want to
announce in your area. This might be an interesting new feature, or it could be something
the user should be aware of (compatibility change, important default changed).
Take a look at CR1’s notes for an idea of what I am looking for:
http://wildfly.org/news/2013/12/21/WildFly8-CR1-Released/
I plan to duplicate most of this content, however, I know there are many other
interesting things I did not cover, so this is your opportunity to highlight them.
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev