Bug 993597 - No resource definition Error when accessing PicketLink section of admin console (PicketLink extension)
Summary: No resource definition Error when accessing PicketLink section of admin conso...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER6
: EAP 6.1.1
Assignee: Heiko Braun
QA Contact: Jakub Cechacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-06 09:09 UTC by Jakub Cechacek
Modified: 2015-02-01 23:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-16 20:23:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PLINK-215 0 Major Resolved Picketlink console extension refers to wrong subsystem 2016-08-24 06:18:37 UTC

Description Jakub Cechacek 2013-08-06 09:09:47 UTC
How to reproduce: 

1) Login into console
2) Navigate to Profile -> PicketLink -> Federation
3) Unknown Error 

Unknown error

Unexpected HTTP response: 500

Request
{
    "operation" => "read-resource-description",
    "address" => [
        ("subsystem" => "picketlink"),
        "federation",
        ("federation" => "*"),
        ("identity-provider" => "*")
    ]
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "failure-description" => "JBAS014883: No resource definition is registered for address [
    (\"subsystem\" => \"picketlink\"),
    (\"federation\" => \"*\"),
    (\"identity-provider\" => \"*\")
]",
    "rolled-back" => true
}

Comment 1 Heiko Braun 2013-08-06 09:14:46 UTC
that's fixed in HAL 1.5.6

Comment 2 Heiko Braun 2013-08-06 09:15:57 UTC
Fixed with https://bugzilla.redhat.com/show_bug.cgi?id=991396

Comment 3 Jakub Cechacek 2013-08-19 08:42:33 UTC
Verified in 6.1.1.ER6


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