[wsf-c-dev] [jira] Updated: (WSFC-129) Security scenario 6 fails
with guththila
on Apache2 on Windows when IssuerSerial is selected as the
securityTokenReference
Evanthika Amarasiri (JIRA)
jira at wso2.org
Thu Sep 6 22:38:48 PDT 2007
[ http://www.wso2.org/jira/browse/WSFC-129?page=all ]
Evanthika Amarasiri updated WSFC-129:
-------------------------------------
Description:
1. The security scenario 6 fails with guththila on Apache2.2.4
2. "Issuer Serial" is selected as the securityTokenReference on the client side as well as the server side
When the request is sent, it gives out a soap fault saying "NULL parameter was passed when a non NULL parameter was expected" (Please fix this message as well)
When checked through TCPMon, you can see that there are garbage characters
was:
1. The security scenario 6 fails with guththila on Apache2.2.4
2. "Issuer Serial" is selected as the securityTokenReference on the client side as well as the server side
When the request is sent, it gives out a soap fault saying "NULL parameter was passed when a non NULL parameter was expected" (Please fix this message as well)
When checked through TCPMon, you can see that there are garbage characters
<ds:X509IssuerName>O=OASIS, CN=OASIS Interop Test CA</:X509IssuerName>
> Security scenario 6 fails with guththila on Apache2 on Windows when IssuerSerial is selected as the securityTokenReference
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WSFC-129
> URL: http://www.wso2.org/jira/browse/WSFC-129
> Project: WSO2 WSF/C
> Issue Type: Bug
> Components: Apache Rampart/C (Security)
> Affects Versions: 1.1.0
> Environment: Windows XP, guththila, Apache2.2.4
> Reporter: Evanthika Amarasiri
>
> 1. The security scenario 6 fails with guththila on Apache2.2.4
> 2. "Issuer Serial" is selected as the securityTokenReference on the client side as well as the server side
> When the request is sent, it gives out a soap fault saying "NULL parameter was passed when a non NULL parameter was expected" (Please fix this message as well)
> When checked through TCPMon, you can see that there are garbage characters
--
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
More information about the Wsf-c-dev
mailing list