Bug 1010659 - RBAC: Failed to create security context for jmx
Summary: RBAC: Failed to create security context for jmx
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ER3
: EAP 6.2.0
Assignee: Heiko Braun
QA Contact: Jakub Cechacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-22 10:25 UTC by Jakub Cechacek
Modified: 2015-02-01 23:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:22:06 UTC
Type: Bug


Attachments (Terms of Use)

Description Jakub Cechacek 2013-09-22 10:25:14 UTC
When accessing Profiles - Core - JMX  the following error is thrown

Failed to create security context for jmx, fallback to temporary read-only context

Unexpected HTTP response: 500

Request
{
    "operation" => "composite",
    "address" => [],
    "steps" => [{
        "address" => [
            ("profile" => "full"),
            ("subsystem" => "jmx")
        ],
        "operation" => "read-resource-description",
        "recursive-depth" => 2,
        "access-control" => "trim-descriptions",
        "operations" => true
    }]
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "result" => {"step-1" => {
        "outcome" => "failed",
        "failure-description" => "JBAS014749: Operation handler failed: null",
        "rolled-back" => true
    }},
    "failure-description" => {"domain-failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014749: Operation handler failed: null"}}},
    "rolled-back" => true
}


I have also checked this against WF master - JMX is inaccessible in WF and "Access Denied" popup is shown to everyone except superuser

Comment 3 Jakub Cechacek 2013-10-01 08:42:12 UTC
Verified 6.2.0.ER3


Note You need to log in before you can comment on or make changes to this bug.