Bug 1155492 - PicketLink Subsystem dissapears after removing last federation after reload
Summary: PicketLink Subsystem dissapears after removing last federation after reload
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: PicketLink
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR7
: EAP 6.4.0
Assignee: Pedro Igor
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-22 08:57 UTC by Ondrej Lukas
Modified: 2019-08-19 12:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:44:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1147375 0 unspecified CLOSED Empty PicketLink Subsystem disappears after reload 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker EAP6-182 0 Major Ready for QA Transition PicketLink subsystems from tech preview to production support 2016-01-04 10:02:55 UTC

Internal Links: 1147375

Description Ondrej Lukas 2014-10-22 08:57:55 UTC 
When last federation from PicketLink Federation Subsystem is removed then PicketLink Federation Subsystem is removed from XML configuration too (but stays in model). Then reload operation causes dissapear of this subsystem.

In correct behavior PicketLink Federation Subsystem stays written in XML configuration after removing of its last federation.

Same situation occures in PicketLink Identity Management Subsystem (removing last partition-manager causes same issue).
Comment 2 JBoss JIRA Server 2014-10-22 09:08:14 UTC 
Ondrej Lukas <olukas> updated the status of jira EAP6-182 to Reopened
Comment 3 Pedro Igor 2014-10-22 13:05:32 UTC 
https://github.com/jbossas/jboss-eap/pull/1838
Comment 4 Ondrej Lukas 2014-11-03 07:22:09 UTC 
Verified in EAP 6.4.0.DR7.
Comment 5 JBoss JIRA Server 2014-11-05 07:05:42 UTC 
Rostislav Svoboda <rsvoboda> updated the status of jira EAP6-182 to Resolved
Note You need to log in before you can comment on or make changes to this bug.