Hide Forgot
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
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.
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.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1753 This PDF shows the proposed approach for default & user-specified security configurations.
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.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1753 Fixes include fixes for SWITCHYARD-1754 as well.
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.
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1753 pushed
Verified with JBDS-IS 7.0.0.CR1
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1753 to Closed