[jboss-jira] [JBoss JIRA] (WFLY-3017) OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config
Brian Stansberry (JIRA)
issues at jboss.org
Tue Feb 25 23:17:47 EST 2014
[ https://issues.jboss.org/browse/WFLY-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12948147#comment-12948147 ]
Brian Stansberry commented on WFLY-3017:
----------------------------------------
Same for removeResource and addResource. The latter probably doesn't matter much, since runtime-only resources are typically not added via mgmt ops. But I'll fix it anyway.
> OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-3017
> URL: https://issues.jboss.org/browse/WFLY-3017
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 8.0.1.Final
>
>
> The readResourceForUpdate impl makes a few assumptions regarding the fact that a given Resource represents persistent config (i.e. Resource.isRuntime() == true):
> 1) It calls rejectUserDomainServerUpdates() which means an OSH running on a server could not call this.
> 2) It calls authorize(false, READ_WRITE_CONFIG) which means an OSH for an op available to the RBAC Operator role could not call this.
> Places this impacts include LogStoreProbeHandler and LogStoreTransactionDeleteHandler which should be calling readResourceForUpdate but aren't -- and can't because of this bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list