incubator-stonehenge-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Dewey (JIRA)" <>
Subject [jira] Commented: (STONEHENGE-44) PHP_BS -> DOTNET_OPSSEC interop does not work properly
Date Fri, 01 May 2009 21:45:31 GMT


Ben Dewey commented on STONEHENGE-44:

I tried again today from a fresh build and, as before, the php page returned, but the order
never got closed or processed through .NET.  

Using the bob_cert had no data in the SvcTraceViewer.

I've been looking into the issue a lot and I'm hoping to get a security expert involved. 
Is seems to be related to the fact that the EncryptionKey is loaded by reference:

<xenc:EncryptedKey Id="EncKeyID-04818ef2-e732-44e1" xmlns:xenc="">
    <xenc:EncryptionMethod Algorithm=""></xenc:EncryptionMethod>
    <ds:KeyInfo xmlns:ds="">
      <wsse:SecurityTokenReference xmlns:wsse="">

        <wsse:Reference URI="#CertID-4835f059-ce6f-4de8" ValueType=""></wsse:Reference>


Is there a way to modify the policy.xml file so that the SecurityToken, gets supplied as a
Key Identifier, this is the data that is being sent to WSAS/PHP from .NET

      <e:EncryptedKey Id="uuid-914d7d40-322e-4228-ba8c-d286ff9bc88c-1" xmlns:e="">
        <e:EncryptionMethod Algorithm="">
          <DigestMethod Algorithm="" xmlns=""/>
        <KeyInfo xmlns="">

            <o:KeyIdentifier ValueType="">NQM0IBvuplAtETQvk+6gn8C13wE=</o:KeyIdentifier>

          <e:DataReference URI="#_1"/>

> PHP_BS -> DOTNET_OPSSEC interop does not work properly
> ------------------------------------------------------
>                 Key: STONEHENGE-44
>                 URL:
>             Project: Stonehenge
>          Issue Type: Bug
>          Components: DOTNET_OPS, PHP_BS
>            Reporter: S.Uthaiyashankar
>             Fix For: M1
>         Attachments: bob_cert.cert
> PHP_BS and DOTNET_OPSSEC are using different certificates, policies. Have to include
a CustomBinding in .NET order processor service to include the policy and certificate. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message