Interop and test Status

[Werner Dittmann <We...@t-online.de>]

 Dims, all

 fixed some problems with interops, mainly small things as you can see.
 All Unti tests ok, all interop tests in local mode ok.

 Scenarios 1,2: Ok with MSFT
Scenarios 3-6 MSFT complains about "Timestamp Created in the past"????
even  if we use Zulu time

Scenarios 3-6: ok with  "http://nyarlathotep.merlin.org/interop/4.soap",
not tested with scenarios 1 and 2.

 Scenario 7: above address complains about "wrong name for STRTransform",
seems  another namespace problem ... they should really produce a list
of all valid names,  identifiers etc at OASIS as normative and publish it.
Not testet with other addresses.

 No success with interop service at
"http://192.18.49.131:8080/pingservice/Ping1". They send the
certificate for WSSTest1 in their response, we expect the cert for
WSSTest2. The other interop services send WSSTest2. Thus
we got a problem with the certificate.

 In the deploymnet descriptors: be aware of blanks in encryptionParts or
signature parts. Even if the calls trim() on the string... somehow a leading
blank wasn't  removed.

 Regards,
Werner

Re: Interop and test Status

[Werner Dittmann <We...@t-online.de>]

Just checked the problem with the Timestamp:
I did a fix with the timestamp (the Expires was missing). Maybe
that's what confuses the MSFT service. But Expires is 5 minutes
aheaded of Created....but they tell that Created is in the past...???

Werner

----- Original Message -----
From: "Werner Dittmann" <We...@t-online.de>
To: <ws...@apache.org>
Sent: Thursday, March 11, 2004 11:50 PM
Subject: Interop and test Status


>
>
>  Dims, all
>
>  fixed some problems with interops, mainly small things as you can see.
>  All Unti tests ok, all interop tests in local mode ok.
>
>  Scenarios 1,2: Ok with MSFT
> Scenarios 3-6 MSFT complains about "Timestamp Created in the past"????
> even  if we use Zulu time
>
> Scenarios 3-6: ok with  "http://nyarlathotep.merlin.org/interop/4.soap",
> not tested with scenarios 1 and 2.
>
>  Scenario 7: above address complains about "wrong name for STRTransform",
> seems  another namespace problem ... they should really produce a list
> of all valid names,  identifiers etc at OASIS as normative and publish it.
> Not testet with other addresses.
>
>  No success with interop service at
> "http://192.18.49.131:8080/pingservice/Ping1". They send the
> certificate for WSSTest1 in their response, we expect the cert for
> WSSTest2. The other interop services send WSSTest2. Thus
> we got a problem with the certificate.
>
>  In the deploymnet descriptors: be aware of blanks in encryptionParts or
> signature parts. Even if the calls trim() on the string... somehow a
leading
> blank wasn't  removed.
>
>  Regards,
> Werner
>
>