Bug 1150987 - Two identity-provider and service-providers elements can be added to one federation in PicketLink Subsystem
Summary: Two identity-provider and service-providers elements can be added to one fede...
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: DR6
: EAP 6.4.0
Assignee: Pedro Igor
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-09 11:26 UTC by Ondrej Lukas
Modified: 2019-08-19 12:43 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:43:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
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:07 UTC
Red Hat Issue Tracker WFLY-3978 0 Major Resolved PicketLink Subsystem EAP 6.4 Issues 2016-03-17 08:36:17 UTC

Description Ondrej Lukas 2014-10-09 11:26:17 UTC 
According to XSD (wildfly-picketlink-federation_1_1.xsd) maxOccurs of identity-provider is 1. However, there can be added more identity-provider elements through CLI or by editing configuration in XML. Adding of second identity-provider element should cause failure.

Also more service-providers elements can be added by editing configuration in XML. It should cause failure in start of server because it is invalid XML configuration.
Comment 1 JBoss JIRA Server 2014-10-14 13:01:23 UTC 
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Resolved
Comment 2 JBoss JIRA Server 2014-10-14 13:26:49 UTC 
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Reopened
Comment 3 Pedro Igor 2014-10-17 15:31:22 UTC 
https://github.com/jbossas/jboss-eap/pull/1810
Comment 4 JBoss JIRA Server 2014-10-17 18:38:37 UTC 
Kabir Khan <kabir.khan> updated the status of jira EAP6-182 to Resolved
Comment 5 JBoss JIRA Server 2014-10-22 09:08:08 UTC 
Ondrej Lukas <olukas> updated the status of jira EAP6-182 to Reopened
Comment 6 Ondrej Lukas 2014-10-22 11:49:18 UTC 
Verified in EAP 6.4.0.DR6.
Comment 7 JBoss JIRA Server 2014-11-05 07:05:36 UTC 
Rostislav Svoboda <rsvoboda> updated the status of jira EAP6-182 to Resolved
Comment 8 JBoss JIRA Server 2016-03-17 08:36:18 UTC 
Pedro Igor <pigor.craveiro> updated the status of jira WFLY-3978 to Resolved
Note You need to log in before you can comment on or make changes to this bug.