Bug 1015483

Summary:	Cannot set security configuration on security policy tab
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Andrej Podhradsky <apodhrad>
Component:	SwitchYard Editor	Assignee:	Brian Fitzpatrick <bfitzpat>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Sedlacek <jsedlace>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0 GA	CC:	ldimaggi, oskutka, rcernich, soa-p-jira
Target Milestone:	ER7
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-06 15:25:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Andrej Podhradsky 2013-10-04 11:22:36 UTC

Description of problem:
Cannot set security configuration on security policy tab if there is only one security configuration defined. You can select security condition only if there are at least 2 configurations.

Version-Release number of selected component (if applicable):
JBTIS 4.1.3.Beta3 (contains switchyard 1.1.0.v20130912-2244-H393-M2) 

How reproducible:
always

Steps to Reproduce:
1. Create new security configuration
2. Go to properties and try to select it on security policy tab

Actual results:
The combo box is empty and disabled

Expected results:
We should be able to select the created security configuration or it should automatically detect the configuration

Comment 1 JBoss JIRA Server 2013-10-04 11:33:35 UTC

Andrej Podhradsky <apodhrad> made a comment on jira SWITCHYARD-1753

Ok, now I see that the first security configuration should be named 'default'. IMHO we should allow user to select whatever name he wants.

Comment 2 JBoss JIRA Server 2013-10-07 16:05:41 UTC

Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1753

There's definitely a weird issue here. I have it fixed, but need to add the ability to deselect a security configuration, which doesn't exist currently.

Comment 3 JBoss JIRA Server 2013-10-07 18:00:09 UTC

Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1753

This PDF shows the proposed approach for default & user-specified security configurations.

Comment 4 JBoss JIRA Server 2013-10-07 19:19:07 UTC

Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1753

Have a branch ready to go, just waiting for some clarification from David Ward on a couple of things before I submit the PR.

Comment 5 JBoss JIRA Server 2013-10-07 19:19:26 UTC

Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1753

Fixes include fixes for SWITCHYARD-1754 as well.

Comment 6 JBoss JIRA Server 2013-10-09 14:15:33 UTC

Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1753

So we have three states:

* Contract with no security attribute and no security configuration defined by the user. Uses default security configuration in the runtime.
* User specifies security configuration with name "default", which overrides the default security configuration in the runtime. Contract with no security attribute uses the new default even if not specified.
* User specifies security configuration with other name and can specify that specific security configuration by name on any contract to override the default, whether previously overridden by the user or not.

These three states are now better covered in the UI.

Comment 7 JBoss JIRA Server 2013-10-15 20:06:34 UTC

Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1753

pushed

Comment 8 Andrej Podhradsky 2013-12-16 08:07:18 UTC

Verified with JBDS-IS 7.0.0.CR1

Comment 9 JBoss JIRA Server 2014-06-16 23:48:11 UTC

Keith Babo <kbabo> updated the status of jira SWITCHYARD-1753 to Closed