[wsas-java-dev] [jira] Commented: (WSAS-144) The https transport binding not removed after assiging the security scenario "Sign-only"

[Saminda Wishwajith Abeyruwan (JIRA)]

    [ http://www.wso2.org/jira/browse/WSAS-144?page=comments#action_12312 ] 
            
Saminda Wishwajith Abeyruwan  commented on WSAS-144:
----------------------------------------------------

Fixed in WSAS 2.0 release

> The https transport binding not removed after assiging the security scenario "Sign-only"
> ----------------------------------------------------------------------------------------
>
>                 Key: WSAS-144
>                 URL: http://www.wso2.org/jira/browse/WSAS-144
>             Project: WSO2 WSAS
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 1-1-rc4
>         Environment: Windows XP, JDK 1.5.0_06, Firefox version 1.5.0.8, jakarta-tomcat-5.0.30, wso2wsas-servlet-edition-java-1.1
>            Reporter: Evanthika Amarasiri
>         Assigned To: Saminda Wishwajith Abeyruwan 
>            Priority: Minor
>             Fix For: 1-1-rc4
>
>
> Below are the steps followed to recreate the issue
> 1. Go to "Services > Select a service [echo] > Click on "Manage Security Configuration" and assign the security configuration "UsernameToken with Timestamp over HTTPS"
> 2. Next assign the security scenario "Sign on" to the same service
> 3. Now go to "Manage Transports" of that particular service
> 4. Remove the transports binding "https" and it will give the message "Removed https transport binding for Adding service" but the https transport binding is still displayed in the management console
> 5. If you try to remove the binding for the second time only it would be removed

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira