[
https://issues.jboss.org/browse/WFLY-4880?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-4880:
-----------------------------------
Permissions in deployments (like most deployment constructs) cannot be referenced from the
management model; this problem is neither introduced nor solved by this bug or its
resolution. Deployments can declare additional permissions using the standard
{{permissions.xml}} or our specific {{jboss-permissions.xml}}.
Permissions are not associated with security domains.
Since permission sets would be modelled as complex attributes, you wouldn't need to
have {{/deployment-permissions=xxx}} at all. Instead you'd edit the attribute using
the regular read/write-attribute operations and their variants.
Permission names are not persisted in the domain model
------------------------------------------------------
Key: WFLY-4880
URL:
https://issues.jboss.org/browse/WFLY-4880
Project: WildFly
Issue Type: Bug
Components: Domain Management, Security Manager
Affects Versions: 10.0.0.Alpha4
Reporter: Josef Cacek
Assignee: Kabir Khan
Priority: Blocker
Permission names used in the {{security-manager}} subsystem model are not persisted. It
can simply lead to non-bootable server configuration.
Expected behavior:
The names used for permission model nodes are persisted in the model (e.g. in an
{{alias}} attribute).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)