[ http://wso2.org/jira/browse/WSAS-623?page=all ]
Nandana Mihindukulasooriya updated WSAS-623:
--------------------------------------------
Attachment: WSAS-623.patch
scenario12-policy.xml
scenario13-policy.xml
Three scenarios added.
1) Anonymous - Sign (scenario9)
Messages are signed using a symmetric key encrypted for the service's
certificate. No client authentication. ( clients needn't to process a
certificate )
2) Anonymous - Sign and encrypt (scenario10)
Messages are signed using a symmetric key encrypted for the service's
certificate. No client authentication.
3) Sign and encrypt - Username Token Authentication (scenario11)
Messages are signed using a symmetric key encrypted for the service's
certificate. Username token is used for authentication.
Previous scenarios ( 9, 10, 11 ) was renamed to scenario 12, 13, 15 to keep WSS
1.1 scenarios next to WSS 1.0 scenarios to make the list more logical.
> Add WS-Sec 1.1 scenarios into the list of available security scenarios
> ----------------------------------------------------------------------
>
> Key: WSAS-623
> URL: http://wso2.org/jira/browse/WSAS-623
> Project: WSO2 WSAS
> Issue Type: Task
> Reporter: Afkham Azeez
> Assigned To: Nandana Mihindukulasooriya
> Priority: Critical
> Fix For: 2.2
>
> Attachments: scenario12-policy.xml, scenario13-policy.xml,
> scenario14-policy.xml, scenario15-policy.xml, WSAS-623.patch
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
