incubator-stonehenge-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "S.Uthaiyashankar (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (STONEHENGE-44) PHP_BS -> DOTNET_OPSSEC interop does not work properly
Date Mon, 04 May 2009 09:23:30 GMT

     [ https://issues.apache.org/jira/browse/STONEHENGE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

S.Uthaiyashankar resolved STONEHENGE-44.
----------------------------------------

    Resolution: Fixed
      Assignee: S.Uthaiyashankar

Keys used by PHP/WSAS is changed to the same key used by .NET. 
Custom binding added to DOTNET order processor service. 
Since key is changed in WSAS/PHP, business service's App.config is modified to have new keys.


Now DOTNET_OPSSEC will be in http://localhost:8000/TradeOrderProcessor/sec

> PHP_BS -> DOTNET_OPSSEC interop does not work properly
> ------------------------------------------------------
>
>                 Key: STONEHENGE-44
>                 URL: https://issues.apache.org/jira/browse/STONEHENGE-44
>             Project: Stonehenge
>          Issue Type: Bug
>          Components: DOTNET_OPS, PHP_BS
>            Reporter: S.Uthaiyashankar
>            Assignee: 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.


Mime
View raw message