[RESULTS] [VOTE] Apache Stonehenge M2 Release (take4)
Take4 of the release passed on the Stonehenge Developer list with a vote of 8 +1 votes No 0 votes No -1 votes Thank you everyone for your votes. I will be moving the vote to the Incubator General List now. -Ben Dewey -Original Message- From: Ben Dewey Sent: Wednesday, June 30, 2010 1:23 AM To: stonehenge-dev@incubator.apache.org Subject: [VOTE] Apache Stonehenge M2 Release (take4) Hi, As you may have seen from the incubator general list emails, some items have caused a rebuild and thus a re-vote. I've produces a take4 version of the artifacts and they can be found below. Apache Stonehenge M2 release artifacts are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take4/ Please test, review and vote on the release artifacts for Apache Stonehenge M2 release. Vote open for 72 hours. Please note you will have to vote again (i.e. votes from take1, take2, and take3 do not count). Here is my vote +1. Regards, Ben Dewey
[VOTE] Approve the M2 release of Apache Stonehenge
Hi, The Apache Stonehenge community has voted for the M2 release of Apache Stonehenge. We are now asking the approval from the Incubator PMC to publish the release. Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practice and interoperability. I have uploaded the Apache Stonehenge M2 release artifacts here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ The CHANGELOG is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ChangeLog The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take4/ The release vote on the stonehenge-dev mailing list resulted in 8 +1 votes and no 0 or -1 votes. +1 votes are from *Ben Dewey *Kent Brown *Pablo Cibraro *Selvaratnam Uthaiyashankar *Chintana Wilamuna *Kamaljit Bath *Nick Hauenstein *Scott Golightly Vote Mail Thread is here: http://www.mail-archive.com/stonehenge-dev@incubator.apache.org/msg02559.html More information about the project can be found here: [Incubation Status Page] http://incubator.apache.org/projects/stonehenge.html [Project Page] http://incubator.apache.org/stonehenge/ Please vote to approve this release. [] +1 Publish [] 0 no opinion [] -1 Don't publish (and reasons why) Regards, -Ben Dewey
RE: [VOTE] Apache Stonehenge M2 Release (take4)
All, I had to update the GnuPG signatures on this take4 build. The artifacts have not changed, but the new signatures can be found here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ The new key file is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/KEYS There is no need to re-vote we will proceed as scheduled. -Ben Dewey -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Wednesday, June 30, 2010 1:23 AM To: stonehenge-dev@incubator.apache.org Subject: [VOTE] Apache Stonehenge M2 Release (take4) Hi, As you may have seen from the incubator general list emails, some items have caused a rebuild and thus a re-vote. I've produces a take4 version of the artifacts and they can be found below. Apache Stonehenge M2 release artifacts are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take4/ Please test, review and vote on the release artifacts for Apache Stonehenge M2 release. Vote open for 72 hours. Please note you will have to vote again (i.e. votes from take1, take2, and take3 do not count). Here is my vote +1. Regards, Ben Dewey
[jira] Resolved: (STONEHENGE-129) Incorrect/missing SVN eol-style properties
[ https://issues.apache.org/jira/browse/STONEHENGE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-129. -- Resolution: Fixed This issues has been committed (r958838). Incorrect/missing SVN eol-style properties -- Key: STONEHENGE-129 URL: https://issues.apache.org/jira/browse/STONEHENGE-129 Project: Stonehenge Issue Type: Bug Affects Versions: M2 Reporter: Sebb Fix For: M2 Attachments: stonehenge_m2_incubator_take3.sh Incorrect/missing SVN properties - patch script to follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] Apache Stonehenge M2 Release (take4)
Hi, As you may have seen from the incubator general list emails, some items have caused a rebuild and thus a re-vote. I've produces a take4 version of the artifacts and they can be found below. Apache Stonehenge M2 release artifacts are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/ The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take4/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take4/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take4/ Please test, review and vote on the release artifacts for Apache Stonehenge M2 release. Vote open for 72 hours. Please note you will have to vote again (i.e. votes from take1, take2, and take3 do not count). Here is my vote +1. Regards, Ben Dewey
[jira] Updated: (STONEHENGE-129) Incorrect/missing SVN eol-style properties
[ https://issues.apache.org/jira/browse/STONEHENGE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey updated STONEHENGE-129: - Affects Version/s: M2 Fix Version/s: M2 Incorrect/missing SVN eol-style properties -- Key: STONEHENGE-129 URL: https://issues.apache.org/jira/browse/STONEHENGE-129 Project: Stonehenge Issue Type: Bug Affects Versions: M2 Reporter: Sebb Fix For: M2 Attachments: stonehenge_m2_incubator_take3.sh Incorrect/missing SVN properties - patch script to follow. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULTS] [VOTE] Apache Stonehenge M2 Release (take3)
Take3 of the release passed on the Stonehenge Developer list with a vote of 8 +1 votes No 0 votes No -1 votes Thank you everyone for your votes. I will be moving the vote to the Incubator General List now. -Ben Dewey -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Thursday, June 24, 2010 2:59 PM To: stonehenge-dev@incubator.apache.org Subject: [VOTE] Apache Stonehenge M2 Release (take3) Hi, I've produces a take3 version of the artifacts and they can be found below. Apache Stonehenge M2 release artifacts are here: http://people.apache.org/~bendewey/stonehenge/m2/take3/ The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take3/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take3/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take3/ Please test, review and vote on the release artifacts for Apache Stonehenge M2 release. Vote open for 72 hours. Please note you will have to vote again (i.e. votes from take1 and take2 do not count). Here is my vote +1. Regards, Ben Dewey
[VOTE] Apache Stonehenge M2 Release (take2)
Hi, Everyone, Shankar notices some issues with the first set of artifacts. I've produces a take2 version of the artifacts and they can be found below. Apache Stonehenge M2 release artifacts are here: http://people.apache.org/~bendewey/stonehenge/m2/take2/ The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take2/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take2/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take2/ Please test, review and vote on the release artifacts for Apache Stonehenge M2 release. Vote open for 72 hours. Please note you will have to vote again (i.e. votes from take1 do not count). Here is my vote +1. Regards, Ben Dewey
[CANCELLED] [VOTE] Apache Stonehenge M2 Release (take2)
I apologize, I noticed another issue with this release. We were missing the binary packaging of the .NET Passive STS. Please stay tuned for take3 and disregard this vote. -Ben Dewey
[VOTE] Apache Stonehenge M2 Release (take3)
Hi, I've produces a take3 version of the artifacts and they can be found below. Apache Stonehenge M2 release artifacts are here: http://people.apache.org/~bendewey/stonehenge/m2/take3/ The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take3/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take3/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take3/ Please test, review and vote on the release artifacts for Apache Stonehenge M2 release. Vote open for 72 hours. Please note you will have to vote again (i.e. votes from take1 and take2 do not count). Here is my vote +1. Regards, Ben Dewey
[VOTE] Apache Stonehenge M2 Release
Hi, I have uploaded the Apache Stonehenge M2 release artifacts here: http://people.apache.org/~bendewey/stonehenge/m2/take1/ The key is here: http://people.apache.org/~bendewey/stonehenge/m2/take1/KEYS RAT reports are here: http://people.apache.org/~bendewey/stonehenge/m2/take1/rat_report/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator/ Please test, review and vote on the release artifacts for Apache Stonehenge M2 release. Vote open for 72 hours. Here is my vote +1. Regards, Ben Dewey
RE: Zero M2 Bug Tickets
Great thanks, Do you have a patch for the DB Create Script update? -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Friday, June 18, 2010 11:15 AM To: stonehenge-dev@incubator.apache.org Subject: RE: Zero M2 Bug Tickets Hello, I added steps to the metro install docs to get the certificates imported. We also need to update the DB creation scripts so that the METRO_BS endpoint URI has STS appended to it. I updated to get Pablo's patch applied to my image, but I'm still getting the NPE for calls from METRO_BS. Pablo is going to look at that today, and see if it's a quirk with my setup or an actual issue. - Nick From: Ben Dewey [ben.de...@26ny.com] Sent: Friday, June 18, 2010 6:05 AM To: stonehenge-dev@incubator.apache.org Subject: RE: Zero M2 Bug Tickets Just waiting on Nick to: give the documentation one last look and give approval so I can build the M2 release and put it up for a vote If I don't hear from him shortly I will package the release as is. -Ben Dewey -Original Message- From: Kent Brown [mailto:kent.br...@microsoft.com] Sent: Thursday, June 17, 2010 7:17 PM To: stonehenge-dev@incubator.apache.org Subject: RE: Zero M2 Bug Tickets Woohoo! Anything else holding up doing a release and starting a vote? Kent -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Wednesday, June 16, 2010 8:00 PM To: stonehenge-dev@incubator.apache.org Subject: Zero M2 Bug Tickets JIRA has 0 items pending for M2. -Ben Dewey
[jira] Closed: (STONEHENGE-128) DB: Create script for config db points to incorrect METRO_BS endpoint
[ https://issues.apache.org/jira/browse/STONEHENGE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey closed STONEHENGE-128. Resolution: Fixed Commited in rev.956063 DB: Create script for config db points to incorrect METRO_BS endpoint - Key: STONEHENGE-128 URL: https://issues.apache.org/jira/browse/STONEHENGE-128 Project: Stonehenge Issue Type: Bug Affects Versions: M2 Reporter: Nicholas A Hauenstein Assignee: Nicholas A Hauenstein Priority: Minor Fix For: M2 Attachments: metrobs_dbscript.patch See attached patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-127) Null pointer exception in Order Processor client
[ https://issues.apache.org/jira/browse/STONEHENGE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12879470#action_12879470 ] Ben Dewey commented on STONEHENGE-127: -- Pablo, I've committed this patch. Please verify and close. Thanks, Null pointer exception in Order Processor client Key: STONEHENGE-127 URL: https://issues.apache.org/jira/browse/STONEHENGE-127 Project: Stonehenge Issue Type: Bug Affects Versions: M2 Environment: Metro Reporter: Pablo Mariano Cibraro Attachments: ops.patch The order processor port for the basic http endpoint is missing from the business client configuration in metro. Also, the certificates in the java key store for consuming this service are not well configured. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Final-ish M2 Testing
STONEHENGE-127 should resolve #1. For #2 I added an info block to the documentation page. https://cwiki.apache.org/confluence/display/STONEHENGE/Stonehenge+WSAS+StockTrader+Documentation Nick, Can you get latest, and verify #1. Also, can you give the documentation one last look and give approval so I can build the M2 release and put it up for a vote. Thanks, -Ben Dewey -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Thursday, June 03, 2010 3:46 PM To: stonehenge-dev@incubator.apache.org Subject: RE: Final-ish M2 Testing Nick, Thanks for all your testing this is a huge help and greatly appreciated. We'd really need to focus on releasing something as soon as possible. What are your thoughts here on what is obtainable to fix and what should be documented going forward. My thoughts are: 1) See if we can fix the Null Pointer Exception 2) Document WSO2 not working with WS Sec but leave it as is. Thanks, -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Thursday, June 03, 2010 2:45 PM To: stonehenge-dev@incubator.apache.org Subject: Final-ish M2 Testing I tested most possible M2 communications scenarios with the .NET client in a VM after patching (hopefully) everything that has been found up to this point. The Metro business service is able to return account information, but it looks like there is a failure happening somewhere when actually submitting orders. The WSO2 services look fairly solid as long as we're not using any of the bindings that use messaging security, and they do work with the .NET Active STS. The configuration I'm using on the .NET side is what I just attached to STONEHENGE-124. I did make an endpoint update to point the METRO_BS at /business_service/TradeServiceWsasSTS, as that is what the metro configuration seemed to indicate was necessary. Without this change every action attempted while using METRO_BS resulted in an error saying Unknown target service provider http://apps.stonehenge.dev:8080/business_service/TradeServiceWsas. STS Configuration does not contain meta data for the service. Any thoughts on the NPE I'm seeing when the METRO_BS is trying to communicate with any OPS? DOTNET PASSIVE STS DOTNET_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC PASS o DOTNET_OPSTSEC PASS o METRO_OPS PASS o METRO_OPSSEC PASS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS METRO_BS (METRO ACTIVE STS) Actual endpoint of service to use is /business_service/TradeServiceWsasSTS, docs update required o DOTNET_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSTSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o WSAS_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION PHP_BS (N/A) o DOTNET_OPS PHP NOT INSTALLED ON VM/NOT TESTED o DOTNET_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED o DOTNET_OPSTSEC PHP NOT INSTALLED ON VM/NOT TESTED o METRO_OPS PHP NOT INSTALLED ON VM/NOT TESTED o METRO_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED WSAS_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC FAIL - ORDER STUCK IN OPEN STATUS o DOTNET_OPSTSEC FAIL - PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target o METRO_OPS PASS o METRO_OPSSEC FAIL - ORDER STUCK IN OPEN STATUS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS WSO2 IS PASSIVE STS DOTNET_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC PASS o DOTNET_OPSTSEC PASS o METRO_OPS PASS o METRO_OPSSEC PASS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP
[jira] Closed: (STONEHENGE-113) Documentation for configuring OpenSSO in Metro implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey closed STONEHENGE-113. Resolution: Won't Fix No documenation need for this because OpenSSO is not supported in M2 Documentation for configuring OpenSSO in Metro implementation - Key: STONEHENGE-113 URL: https://issues.apache.org/jira/browse/STONEHENGE-113 Project: Stonehenge Issue Type: Improvement Components: Documentation Affects Versions: M2 Environment: METRO Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: Metro Install Guide.docx, STS Setup manual.docx The documentation for configuring the glasshfish domains and OpenSSO instances required for the Metro implementation requires some more details about specific settings. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-107) Change Trader_Client Active_STS to Use Certificate 'BSL.Com'
[ https://issues.apache.org/jira/browse/STONEHENGE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-107. -- Resolution: Fixed The certificate was update the BSL.Com in #900648, by Pablo Change Trader_Client Active_STS to Use Certificate 'BSL.Com' -- Key: STONEHENGE-107 URL: https://issues.apache.org/jira/browse/STONEHENGE-107 Project: Stonehenge Issue Type: New Feature Affects Versions: M2 Environment: glassfish2, jdk5, metro v2, ant Reporter: Ming Jin Fix For: M2 Currently, the trader client in Metro version of stocktrader uses OPS.Com certificate to talk with Business Service, while .NET version uses BSL.Com instead. We'd better use BSL.Com certificate in Metro version of Trader client, Acitive STS as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Stonehenge Mailing list issue
Daniel, Thanks, You can add me, although we still need more because 3 is preferred[1], Any other volunteers? [1] http://www.apache.org/dev/reporting-issues.html#mail-new-moderators -Ben Dewey -Original Message- From: Daniel Kulp [mailto:dk...@apache.org] Sent: Tuesday, June 15, 2010 10:58 AM To: Ben Dewey Cc: stonehenge-dev@incubator.apache.org Subject: Re: Stonehenge Mailing list issue I just unsubscribed: onl...@bankofamerica.com from the list. BTW: at some point, it would probably be good if we change the moderators/owners of the lists to be members of the Stonehenge community itself. Are there a couple of folks that would like to volunteer to be moderators? Dan On Tuesday 15 June 2010 10:42:22 am Ben Dewey wrote: Hi, We keep getting an automated reply from 'onl...@bankofamerica.com' whenever anyone sends an email to our Stonehenge-dev@incubator.apache.orgmailto:stonehenge-...@incubator.apache .org mailing list. I'm guessing that someone registered a bankofamerica.com email to our mailing list. Can someone help me get this removed from our list? Ben Dewey -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
RE: Stonehenge Mailing list issue
Matthew, Thanks so much for you enthusiasm. I think we need committers only for this role. We are happy to have you on board. Please review the steps here and after making some contributions we'll see what we can do to get you committer access. [1] http://apache.org/dev/ [2] http://apache.org/dev/contributors.html -Ben Dewey -Original Message- From: Matthew Brylka [mailto:m...@tynenet.co.uk] Sent: Tuesday, June 15, 2010 12:01 PM To: stonehenge-dev@incubator.apache.org Cc: Daniel Kulp Subject: Re: Stonehenge Mailing list issue I'm quite new to the project, but I could do it. Preferable would be good to have people from various continents (2/2 US/EU). I'm GMT / London. Kind Regards, Maciej Brylka On 15 June 2010 16:14, Ben Dewey ben.de...@26ny.com wrote: Daniel, Thanks, You can add me, although we still need more because 3 is preferred[1], Any other volunteers? [1] http://www.apache.org/dev/reporting-issues.html#mail-new-moderators -Ben Dewey -Original Message- From: Daniel Kulp [mailto:dk...@apache.org] Sent: Tuesday, June 15, 2010 10:58 AM To: Ben Dewey Cc: stonehenge-dev@incubator.apache.org Subject: Re: Stonehenge Mailing list issue I just unsubscribed: onl...@bankofamerica.com from the list. BTW: at some point, it would probably be good if we change the moderators/owners of the lists to be members of the Stonehenge community itself. Are there a couple of folks that would like to volunteer to be moderators? Dan On Tuesday 15 June 2010 10:42:22 am Ben Dewey wrote: Hi, We keep getting an automated reply from 'onl...@bankofamerica.com' whenever anyone sends an email to our Stonehenge-dev@incubator.apache.orgmailto:stonehenge-...@incubator.apache .org mailing list. I'm guessing that someone registered a bankofamerica.com email to our mailing list. Can someone help me get this removed from our list? Ben Dewey -- Daniel Kulp dk...@apache.org http://dankulp.com/blog -- Matthew Brylka TyneNet Ltd Email m...@tynenet.co.uk Web https://www.tynenet.co.uk This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient[s]. If you are not the intended recipient[s] please note that any distribution, copying or use of this communication, or the information in it, is strictly prohibited. If you have received this communication in error please notify us by telephone 08444151097 or e-mail i...@tynenet.co.uk and then destroy the e-mail and any copies of it. This communication is from TyneNet (U.K.) Ltd of 21 Southernwood, DH8 6GD Consett. Our website is www.tynenet.co.uk
RE: Introduction
Welcome aboard. -Ben Dewey -Original Message- From: Matthew Brylka [mailto:m...@tynenet.co.uk] Sent: Tuesday, June 15, 2010 1:02 PM To: stonehenge-dev@incubator.apache.org Subject: Introduction Hi Guys, Quick intro. My name is Maciej (aka Matthew) and I'm a security specialist. I'll be keeping an eye on security within the project and various implementations. We want people to implement secure SOA solutions. I'll be also contributing to the PHP part of the project. Kind Regards -- Maciej Brylka
RE: [Vote] Grant committer status to Nicholas A Hauenstein
+1 with enthusiasm. -Ben Dewey -Original Message- From: Kamaljit Bath [mailto:kamaljit.b...@microsoft.com] Sent: Friday, June 04, 2010 2:34 PM To: stonehenge-dev@incubator.apache.org Subject: [Vote] Grant committer status to Nicholas A Hauenstein I would like to start a formal vote to grant committer status to Nick. This has already been discussed in the Stonehenge private list and we have found no objections. Nick has been engaged with Stonehenge dev community for a long time now. He has 1- Produced installation and configuration documentation for M2 2- Tested interop between all stacks for M2 Specifically, he has made patches to the following issues SH-125, SH-124, SH-123, SH-122, SH-120, SH-119, SH-112, SH-110 Please vote +1, 0, or -1 (with comments) on this vote. Here is a +1 vote from me. kamal
RE: [Vote] Grant committer status to Pablo Cibraro
+1 with enthusiasm. -Ben Dewey -Original Message- From: Kamaljit Bath [mailto:kamaljit.b...@microsoft.com] Sent: Friday, June 04, 2010 2:38 PM To: stonehenge-dev@incubator.apache.org Subject: [Vote] Grant committer status to Pablo Cibraro I would like to start a formal vote to grant committer status to Pablo. This has already been discussed in the Stonehenge private list and we have found no objections. Pablo has been engaged with Stonehenge dev community for a long time now. He has 1- built prototype for M3 2- authored architecture/design document for M3 3- tested interop between all stacks during M1 and M2 4- tpgraded the specs used from contributed versions to be ratified 5- implemented claims based security in .NET and enabled interop with Metro, helped the debug issues between .NET and Java Specifically, he has made patches to the following issues SH-117, SH-116, SH-115, SH-114, SH-113, SH-109, SH-106, SH-104, SH-103, SH-102 Please vote +1, 0, or -1 (with comments) on this vote. Here is a +1 vote from me. kamal
RE: Final-ish M2 Testing
Can someone on the Metro Team respond to this? Jiandong? Thanks, Ben Dewey -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Thursday, June 03, 2010 3:46 PM To: stonehenge-dev@incubator.apache.org Subject: RE: Final-ish M2 Testing Nick, Thanks for all your testing this is a huge help and greatly appreciated. We'd really need to focus on releasing something as soon as possible. What are your thoughts here on what is obtainable to fix and what should be documented going forward. My thoughts are: 1) See if we can fix the Null Pointer Exception 2) Document WSO2 not working with WS Sec but leave it as is. Thanks, -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Thursday, June 03, 2010 2:45 PM To: stonehenge-dev@incubator.apache.org Subject: Final-ish M2 Testing I tested most possible M2 communications scenarios with the .NET client in a VM after patching (hopefully) everything that has been found up to this point. The Metro business service is able to return account information, but it looks like there is a failure happening somewhere when actually submitting orders. The WSO2 services look fairly solid as long as we're not using any of the bindings that use messaging security, and they do work with the .NET Active STS. The configuration I'm using on the .NET side is what I just attached to STONEHENGE-124. I did make an endpoint update to point the METRO_BS at /business_service/TradeServiceWsasSTS, as that is what the metro configuration seemed to indicate was necessary. Without this change every action attempted while using METRO_BS resulted in an error saying Unknown target service provider http://apps.stonehenge.dev:8080/business_service/TradeServiceWsas. STS Configuration does not contain meta data for the service. Any thoughts on the NPE I'm seeing when the METRO_BS is trying to communicate with any OPS? DOTNET PASSIVE STS DOTNET_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC PASS o DOTNET_OPSTSEC PASS o METRO_OPS PASS o METRO_OPSSEC PASS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS METRO_BS (METRO ACTIVE STS) Actual endpoint of service to use is /business_service/TradeServiceWsasSTS, docs update required o DOTNET_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSTSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o WSAS_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION PHP_BS (N/A) o DOTNET_OPS PHP NOT INSTALLED ON VM/NOT TESTED o DOTNET_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED o DOTNET_OPSTSEC PHP NOT INSTALLED ON VM/NOT TESTED o METRO_OPS PHP NOT INSTALLED ON VM/NOT TESTED o METRO_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED WSAS_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC FAIL - ORDER STUCK IN OPEN STATUS o DOTNET_OPSTSEC FAIL - PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target o METRO_OPS PASS o METRO_OPSSEC FAIL - ORDER STUCK IN OPEN STATUS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS WSO2 IS PASSIVE STS DOTNET_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC PASS o DOTNET_OPSTSEC PASS o METRO_OPS PASS o METRO_OPSSEC PASS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS METRO_BS (METRO ACTIVE STS) Actual endpoint of service to use is /business_service/TradeServiceWsasSTS, docs update required o DOTNET_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o
RE: Final-ish M2 Testing
Nick, Thanks for all your testing this is a huge help and greatly appreciated. We'd really need to focus on releasing something as soon as possible. What are your thoughts here on what is obtainable to fix and what should be documented going forward. My thoughts are: 1) See if we can fix the Null Pointer Exception 2) Document WSO2 not working with WS Sec but leave it as is. Thanks, -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Thursday, June 03, 2010 2:45 PM To: stonehenge-dev@incubator.apache.org Subject: Final-ish M2 Testing I tested most possible M2 communications scenarios with the .NET client in a VM after patching (hopefully) everything that has been found up to this point. The Metro business service is able to return account information, but it looks like there is a failure happening somewhere when actually submitting orders. The WSO2 services look fairly solid as long as we're not using any of the bindings that use messaging security, and they do work with the .NET Active STS. The configuration I'm using on the .NET side is what I just attached to STONEHENGE-124. I did make an endpoint update to point the METRO_BS at /business_service/TradeServiceWsasSTS, as that is what the metro configuration seemed to indicate was necessary. Without this change every action attempted while using METRO_BS resulted in an error saying Unknown target service provider http://apps.stonehenge.dev:8080/business_service/TradeServiceWsas. STS Configuration does not contain meta data for the service. Any thoughts on the NPE I'm seeing when the METRO_BS is trying to communicate with any OPS? DOTNET PASSIVE STS DOTNET_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC PASS o DOTNET_OPSTSEC PASS o METRO_OPS PASS o METRO_OPSSEC PASS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS METRO_BS (METRO ACTIVE STS) Actual endpoint of service to use is /business_service/TradeServiceWsasSTS, docs update required o DOTNET_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSTSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o WSAS_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION PHP_BS (N/A) o DOTNET_OPS PHP NOT INSTALLED ON VM/NOT TESTED o DOTNET_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED o DOTNET_OPSTSEC PHP NOT INSTALLED ON VM/NOT TESTED o METRO_OPS PHP NOT INSTALLED ON VM/NOT TESTED o METRO_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPSSEC PHP NOT INSTALLED ON VM/NOT TESTED WSAS_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC FAIL - ORDER STUCK IN OPEN STATUS o DOTNET_OPSTSEC FAIL - PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target o METRO_OPS PASS o METRO_OPSSEC FAIL - ORDER STUCK IN OPEN STATUS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS WSO2 IS PASSIVE STS DOTNET_BS (DOTNET ACTIVE STS) o DOTNET_OPS PASS o DOTNET_OPSSEC PASS o DOTNET_OPSTSEC PASS o METRO_OPS PASS o METRO_OPSSEC PASS o PHP_OPS PHP NOT INSTALLED ON VM/NOT TESTED o PHP_OPSSECPHP NOT INSTALLED ON VM/NOT TESTED o WSAS_OPS PASS o WSAS_OPSSEC PASS METRO_BS (METRO ACTIVE STS) Actual endpoint of service to use is /business_service/TradeServiceWsasSTS, docs update required o DOTNET_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o DOTNET_OPSTSEC FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPS FAIL - NULL POINTER EXCEPTION ON ORDER SUBMISSION o METRO_OPSSEC FAIL - NULL POINTER
[jira] Commented: (STONEHENGE-126) Incorrect Order Processor WSDL in Metro
[ https://issues.apache.org/jira/browse/STONEHENGE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872044#action_12872044 ] Ben Dewey commented on STONEHENGE-126: -- Pablo, This patch seems to be out of date. Can you update you repository and recreate the patch? If you have trouble just attach the latest wsdl. Incorrect Order Processor WSDL in Metro --- Key: STONEHENGE-126 URL: https://issues.apache.org/jira/browse/STONEHENGE-126 Project: Stonehenge Issue Type: Bug Affects Versions: M2 Environment: Metro Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: OPS_WSDL_PATCH.patch The WSDL of order processor service implementation in metro is not compatible with the rest of the implementations (.NET, WSAS). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: AddressAlreadyInUseException when starting TradeOrderProcessor service
Figured you already tried that. Can you try the old fashion way? 1. Run AuthorizeWcfServices.bat and delete all reservations 2. Run OrderProcessorConsoleHost.exe as Administrator manually -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Monday, April 26, 2010 4:14 PM To: stonehenge-dev@incubator.apache.org Subject: RE: AddressAlreadyInUseException when starting TradeOrderProcessor service No such luck this time. That was one of the first things I tried. Tried it again just now, same result. - Nick From: Ben Dewey [ben.de...@26ny.com] Sent: Monday, April 26, 2010 1:02 PM To: stonehenge-dev@incubator.apache.org Subject: RE: AddressAlreadyInUseException when starting TradeOrderProcessor service Nick, I've seen this before, and IIRC a restart fixed it for me. Have you tried that by any chance? -Ben Dewey
RE: AddressAlreadyInUseException when starting TradeOrderProcessor service
Do we think this is distinct to Windows 7? -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Monday, April 26, 2010 4:44 PM To: stonehenge-dev@incubator.apache.org Subject: RE: AddressAlreadyInUseException when starting TradeOrderProcessor service It works with the reservation removed, and without explicitly running as administrator. How should this be documented? - Nick From: Ben Dewey [ben.de...@26ny.com] Sent: Monday, April 26, 2010 1:30 PM To: stonehenge-dev@incubator.apache.org Subject: RE: AddressAlreadyInUseException when starting TradeOrderProcessor service Figured you already tried that. Can you try the old fashion way? 1. Run AuthorizeWcfServices.bat and delete all reservations 2. Run OrderProcessorConsoleHost.exe as Administrator manually -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Monday, April 26, 2010 4:14 PM To: stonehenge-dev@incubator.apache.org Subject: RE: AddressAlreadyInUseException when starting TradeOrderProcessor service No such luck this time. That was one of the first things I tried. Tried it again just now, same result. - Nick From: Ben Dewey [ben.de...@26ny.com] Sent: Monday, April 26, 2010 1:02 PM To: stonehenge-dev@incubator.apache.org Subject: RE: AddressAlreadyInUseException when starting TradeOrderProcessor service Nick, I've seen this before, and IIRC a restart fixed it for me. Have you tried that by any chance? -Ben Dewey
RE: Metro Build Errors
Get Latest and try now, using 'ant deploy' (no STS) -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Monday, April 26, 2010 5:16 PM To: stonehenge-dev@incubator.apache.org Subject: Metro Build Errors I was just running through the Metro install process (sans OpenSSO), but when I got to the point of building the code that is currently in the trunk (by executing: ant STS deploy), I hit quite a few errors during compilation [1]. Is the code that is checked in expected to build right now, or is there still some work pending? Thanks in advance! - Nick [1] Build output: Buildfile: C:\stonehenge\stocktrader\metro\build.xml STS: [echo] copy sts web file [copy] Copying 1 file to C:\stonehenge\stocktrader\metro\trader_client\web\WEB-INF deploy: clean: [delete] Deleting directory C:\stonehenge\stocktrader\metro\business_service\build setup: [mkdir] Created dir: C:\stonehenge\stocktrader\metro\business_service\build [mkdir] Created dir: C:\stonehenge\stocktrader\metro\business_service\build\classes [mkdir] Created dir: C:\stonehenge\stocktrader\metro\business_service\build\war generate-order-processor-client: [wsimport] Consider using depends/produces so that wsimport won't do unnecessary compilation [wsimport] parsing WSDL... [wsimport] [wsimport] [wsimport] [WARNING] SOAP port WSHttpBinding_OrderProcessorService: uses a non-standard SOAP 1.2 binding. [wsimport] line 402 of file:/C:/stonehenge/stocktrader/metro/etc/order_processor/OrderProcessor.wsdl [wsimport] [wsimport] [WARNING] SOAP port CustomBinding_OrderProcessorService: uses a non-standard SOAP 1.2 binding. [wsimport] line 409 of file:/C:/stonehenge/stocktrader/metro/etc/order_processor/OrderProcessor.wsdl [wsimport] [wsimport] [WARNING] SOAP port SecureConversationBinding_OrderProcessorService: uses a non-standard SOAP 1.2 binding. [wsimport] line 416 of file:/C:/stonehenge/stocktrader/metro/etc/order_processor/OrderProcessor.wsdl [wsimport] [wsimport] generating code... [wsimport] [wsimport] [wsimport] compiling code... [wsimport] generate-cs-client: [wsimport] Consider using depends/produces so that wsimport won't do unnecessary compilation [wsimport] parsing WSDL... [wsimport] [wsimport] [wsimport] generating code... [wsimport] [wsimport] [wsimport] compiling code... [wsimport] build: [wsimport] Consider using depends/produces so that wsimport won't do unnecessary compilation [wsimport] parsing WSDL... [wsimport] [wsimport] [wsimport] [WARNING] SOAP port BasicHttpBinding_ITradeServices: uses a non-standard SOAP 1.2 binding. [wsimport] line 507 of file:/C:/stonehenge/stocktrader/metro/etc/business_service/TradeServiceWsas.wsdl [wsimport] [wsimport] [WARNING] SOAP port CustomBinding_ITradeServices: uses a non-standard SOAP 1.2 binding. [wsimport] line 510 of file:/C:/stonehenge/stocktrader/metro/etc/business_service/TradeServiceWsas.wsdl [wsimport] [wsimport] generating code... [wsimport] [wsimport] [wsimport] compiling code... [wsimport] [copy] Copying 2 files to C:\stonehenge\stocktrader\metro\business_service\build\classes [copy] Copying 1 file to C:\stonehenge\stocktrader\metro\business_service\build\classes [copy] Copying 1 file to C:\stonehenge\stocktrader\metro\business_service\build\classes [javac] C:\stonehenge\stocktrader\metro\business_service\build.xml:104: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 23 source files to C:\stonehenge\stocktrader\metro\business_service\build\classes [javac] C:\stonehenge\stocktrader\metro\business_service\build.xml:108: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 6 source files to C:\stonehenge\stocktrader\metro\business_service\build\classes [javac] C:\stonehenge\stocktrader\metro\business_service\build.xml:112: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Compiling 6 source files to C:\stonehenge\stocktrader\metro\business_service\build\classes war: [war] Building war: C:\stonehenge\stocktrader\metro\business_service\build\war\business_service.war deploy-keystore: deploy: [copy] Copying 1 file to C:\Sun\SDK\domains\domain2\autodeploy clean: [delete] Deleting directory C:\stonehenge\stocktrader\metro\order_processor\build setup: [mkdir] Created dir: C:\stonehenge\stocktrader\metro\order_processor\build [mkdir] Created dir: C:\stonehenge\stocktrader\metro\order_processor\build\classes [mkdir] Created dir: C:\stonehenge\stocktrader\metro\order_processor\build\war import-ws: [wsimport] Consider using depends/produces so that wsimport won't do unnecessary compilation [wsimport] parsing WSDL... [wsimport] [wsimport] [wsimport
[jira] Commented: (STONEHENGE-122) Metro implementation of StockTrader attempts to deploy resources to domain2
[ https://issues.apache.org/jira/browse/STONEHENGE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861142#action_12861142 ] Ben Dewey commented on STONEHENGE-122: -- Thanks for the patch Nick. Please verify and resolve. Metro implementation of StockTrader attempts to deploy resources to domain2 --- Key: STONEHENGE-122 URL: https://issues.apache.org/jira/browse/STONEHENGE-122 Project: Stonehenge Issue Type: Bug Affects Versions: M2 Reporter: Nicholas A Hauenstein Assignee: Nicholas A Hauenstein Priority: Minor Fix For: M2 Attachments: domain1patch.patch Original Estimate: 0.08h Remaining Estimate: 0.08h Building the Metro implementation of the StockTrader application results in all of the services being deployed to Glassfish domain2. Since we're not using OpenSSO anymore, this should default to domain1. Patch will be attached momentarily. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (STONEHENGE-121) Proposal for M3
Pablo, I'm not seeing any tests here. Should I be? No tests match the specified criteria. -Ben Dewey From: Pablo Mariano Cibraro (JIRA) [j...@apache.org] Sent: Friday, April 23, 2010 11:50 AM To: stonehenge-dev@incubator.apache.org Subject: [jira] Commented: (STONEHENGE-121) Proposal for M3 [ https://issues.apache.org/jira/browse/STONEHENGE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12860289#action_12860289 ] Pablo Mariano Cibraro commented on STONEHENGE-121: -- A working version of the prototype is available at this address. http://204.152.240.69/Stonehenge Proposal for M3 --- Key: STONEHENGE-121 URL: https://issues.apache.org/jira/browse/STONEHENGE-121 Project: Stonehenge Issue Type: Improvement Components: Documentation Environment: All Reporter: Kent Brown Attachments: Stonehenge M3 Proposal.docx, Stonehenge+M3+Proposal.doc, stonehenge-m3.docx, stonehenge.zip I am creating this to start discussion about M3 plans. I will attach a document of my proposal which has been contributed to and reviewed by several people, but is by no means locked down. Please review and comment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
M2 Release
Everyone, After months of effort, we are hoping to move forward with our M2 Release. I've spoken with a few people off of the list and it seems that due to licensing issues with OpenSSO we are not going to be able to release it anytime in the near future. I, along with many others would like to release and start working M3. In order to do this we felt it best to create a branch, then remove metro trader client from the trunk, and release. Nick Hauenstein is on board and has graciously offered to update the documentation to reflect this. I will perform the branching now and start preparing the code for a release. Please let me know if anyone has any comments. Thanks, Ben Dewey
RE: Status of Ruby Implementation
Chintana, What are your thoughts on removing the ruby implementation from the M2 release? It's extremely out-dated and virtually untested. It can remain in the branch until we have the resources to test it. -Ben Dewey -Original Message- From: Chintana Wilamuna [mailto:chinta...@gmail.com] Sent: Saturday, September 19, 2009 12:16 AM To: stonehenge-dev@incubator.apache.org Subject: Re: Status of Ruby Implementation Nick, It has to be tested with the latest version of Ruby on Rails. Also, it does not take advantage of the new configuration service. Need to fix that as well. Bye, -Chintana -- http://engwar.com/
[jira] Closed: (STONEHENGE-99) Add Support of Username Token over TLS in BSL-OPS
[ https://issues.apache.org/jira/browse/STONEHENGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey closed STONEHENGE-99. --- Resolution: Fixed Based on Pablo's comment this issues has been tested and is fixed. Add Support of Username Token over TLS in BSL-OPS -- Key: STONEHENGE-99 URL: https://issues.apache.org/jira/browse/STONEHENGE-99 Project: Stonehenge Issue Type: New Feature Affects Versions: M2 Environment: glassfish/metro Reporter: Ming Jin Fix For: M2 Attachments: Metro_OrderProcessor_UsernameTLS.patch As Kent suggested, we want to support more ws-security scenarios in BSL talking to OPS, one of which is Username Token over TLS. This issue is about to implement Username Token over TLS in the Metro version. 1. the Certificate OPS.Com is used to establish the SSL channel 2. the original userid and password is used to validate the user -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (STONEHENGE-120) Configuration mapping missing for WSAS in Business Service Console Configuration
[ https://issues.apache.org/jira/browse/STONEHENGE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856156#action_12856156 ] Ben Dewey commented on STONEHENGE-120: -- Nick, This was committed with, http://svn.apache.org/viewvc?view=revisionrevision=916532. Can you verify and close if its working. Configuration mapping missing for WSAS in Business Service Console Configuration Key: STONEHENGE-120 URL: https://issues.apache.org/jira/browse/STONEHENGE-120 Project: Stonehenge Issue Type: Bug Affects Versions: M2 Reporter: Nicholas A Hauenstein Assignee: Nicholas A Hauenstein Fix For: M2 Attachments: STONEHENGE-120.patch Original Estimate: 0.03h Remaining Estimate: 0.03h There is no mapping present in the web.config of the business service console for the WSAS implementation. This will result in an ambiguous match exception whenever the service tries to create a proxy to access the service without specifying a binding configuration. The only reason that this is necessary is because of how the configuration service responses are handled (the BS maps the OPS service identifier to a binding using app settings in the config file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (STONEHENGE-105) Remove SAML token encryption from the .Net impl in order to interoperate with WSO2 Identity Server
[ https://issues.apache.org/jira/browse/STONEHENGE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12856157#action_12856157 ] Ben Dewey commented on STONEHENGE-105: -- Guys, Can we close this issue? Remove SAML token encryption from the .Net impl in order to interoperate with WSO2 Identity Server -- Key: STONEHENGE-105 URL: https://issues.apache.org/jira/browse/STONEHENGE-105 Project: Stonehenge Issue Type: Bug Environment: .Net Reporter: Chintana Wilamuna Fix For: M2 Attachments: passive-sts-web-config.patch, remove-encryption.patch, trader-client-web-config.patch The current implementation of the passive STS, encrypts the SAML token being issued. This creates problems when it comes to configuring WSO2 Identity Server as the passive STS as it cannot encrypt the SAML token. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: WSO2 BS Error
Thanks, Chintana From: Chintana Wilamuna [chinta...@gmail.com] Sent: Tuesday, March 09, 2010 11:47 AM To: stonehenge-dev@incubator.apache.org Subject: Re: WSO2 BS Error On Thu, Mar 4, 2010 at 8:47 AM, Ben Dewey ben.de...@26ny.com wrote: I'm experiencing the following error when interoping with the WSAS BS. I have tried putting the jtds jars in wsas/lib/extensions and wsas/repository/components/lib, and wsas/repository/components/extensions. But I continue to get this error. [snip] Ben, let me try to run the latest code on a new instance. Will get back to you on this. Bye, -Chintana -- Blog: http://engwar.com/ Photos: http://flickr.com/photos/chintana
[jira] Commented: (STONEHENGE-99) Add Support of Username Token over TLS in BSL-OPS
[ https://issues.apache.org/jira/browse/STONEHENGE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841025#action_12841025 ] Ben Dewey commented on STONEHENGE-99: - Pablo, I've committed this I'm having issues building metro right now. Please build and test on your end and resolve it it works. Add Support of Username Token over TLS in BSL-OPS -- Key: STONEHENGE-99 URL: https://issues.apache.org/jira/browse/STONEHENGE-99 Project: Stonehenge Issue Type: New Feature Affects Versions: M2 Environment: glassfish/metro Reporter: Ming Jin Fix For: M2 Attachments: Metro_OrderProcessor_UsernameTLS.patch As Kent suggested, we want to support more ws-security scenarios in BSL talking to OPS, one of which is Username Token over TLS. This issue is about to implement Username Token over TLS in the Metro version. 1. the Certificate OPS.Com is used to establish the SSL channel 2. the original userid and password is used to validate the user -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
WSO2 BS Error
Chintana,
I'm experiencing the following error when interoping with the WSAS BS. I have
tried putting the jtds jars in wsas/lib/extensions and
wsas/repository/components/lib, and wsas/repository/components/extensions. But
I continue to get this error.
Any help would be appreciated.
[2010-03-03 21:26:45,366] ERROR -
org/apache/stonehenge/stocktrader/dal/DAOException
{org.apache.axis2.transport.http.AxisServlet}
java.lang.NoClassDefFoundError:
org/apache/stonehenge/stocktrader/dal/DAOException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
at java.lang.Class.newInstance(Class.java:308)
at
org.apache.axis2.receivers.AbstractMessageReceiver$8.run(AbstractMessageReceiver.java:256)
at
org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:132)
at
org.apache.axis2.receivers.AbstractMessageReceiver.makeNewServiceObject(AbstractMessageReceiver.java:253)
at
org.apache.axis2.receivers.AbstractMessageReceiver.getTheImplementationObject(AbstractMessageReceiver.java:297)
at
org.tempuri.TradeServiceWcfMessageReceiverInOut.invokeBusinessLogic(TradeServiceWcfMessageReceiverInOut.java:39)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:178)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:142)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:135)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: Class Not found :
org.apache.stonehenge.stocktrader.dal.DAOException
at
org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:92)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at
org.apache.axis2.deployment.DeploymentClassLoader.loadClass(DeploymentClassLoader.java:273)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
... 37 more
Thanks,
Ben Dewey
[jira] Commented: (STONEHENGE-119) Changing advanced configuration in .NET doesn't invalidate configuration footer display
[ https://issues.apache.org/jira/browse/STONEHENGE-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12832800#action_12832800 ] Ben Dewey commented on STONEHENGE-119: -- Nick, Thanks, I've committed this patch, with a few minor adjustments. Please test and Resolve the issue if everything works. Changing advanced configuration in .NET doesn't invalidate configuration footer display - Key: STONEHENGE-119 URL: https://issues.apache.org/jira/browse/STONEHENGE-119 Project: Stonehenge Issue Type: Bug Components: DOTNET_CLIENT Affects Versions: M2 Reporter: Nicholas A Hauenstein Assignee: Nicholas A Hauenstein Priority: Minor Fix For: M2 Attachments: STONEHENGE-119.patch Original Estimate: 0h Remaining Estimate: 0h The configuration display does not update whenever the advanced configuration is edited. Patch for this will be attached shortly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: WSO2 Testing
Sorry about that I had it commented out from previous tests. Now, I'm
receiving a 500 error with the following message in the wsas log.
---
[2010-02-10 20:33:47,099] ERROR - Must Understand check failed for header http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : S
ecurity {org.apache.axis2.engine.AxisEngine}
org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.
oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security
Thanks,
-Ben Dewey
-Original Message-
From: Chintana Wilamuna [mailto:chinta...@gmail.com]
Sent: Wednesday, February 10, 2010 12:06 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: WSO2 Testing
On Wed, Feb 10, 2010 at 9:28 AM, Ben Dewey ben.de...@26ny.com wrote:
I tested WSAS again and this time I'm getting the following message
connecting to the active_sts:
General security error (SAML token security failure); nested exception is:
org.opensaml.MalformedException: Subject is invalid, requires either
NameIdentifier or at least one ConfirmationMethod
Ben, make sure signature confirmation is turned off. Line 100 in
Web.config add requireSignatureConfirmation=false attribute.
Bye,
-Chintana
--
Blog: http://engwar.com/
Photos: http://flickr.com/photos/chintana
RE: WSO2 Testing
Chintana,
I've added web.NET.config and web.WSIS.config files that I'm using for the
trader client. Feel free to commit updates to these files there is anything
that looks wrong.
Thanks,
Ben Dewey
-Original Message-
From: Ben Dewey [mailto:ben.de...@26ny.com]
Sent: Wednesday, February 10, 2010 8:43 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: WSO2 Testing
Sorry about that I had it commented out from previous tests. Now, I'm
receiving a 500 error with the following message in the wsas log.
---
[2010-02-10 20:33:47,099] ERROR - Must Understand check failed for header http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : S
ecurity {org.apache.axis2.engine.AxisEngine}
org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.
oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security
Thanks,
-Ben Dewey
-Original Message-
From: Chintana Wilamuna [mailto:chinta...@gmail.com]
Sent: Wednesday, February 10, 2010 12:06 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: WSO2 Testing
On Wed, Feb 10, 2010 at 9:28 AM, Ben Dewey ben.de...@26ny.com wrote:
I tested WSAS again and this time I'm getting the following message
connecting to the active_sts:
General security error (SAML token security failure); nested exception is:
org.opensaml.MalformedException: Subject is invalid, requires either
NameIdentifier or at least one ConfirmationMethod
Ben, make sure signature confirmation is turned off. Line 100 in
Web.config add requireSignatureConfirmation=false attribute.
Bye,
-Chintana
--
Blog: http://engwar.com/
Photos: http://flickr.com/photos/chintana
RE: WSO2 Testing
Did you import the BS.jks and OPS.jks keystores from the WSAS management console? I hadn't, BS.jks imported successfully, but OPS.jks is failing to import with a password of 'yyy' -Ben Dewey
Building lastest Metro src
Pablo/Jiandong, I'm taking another go at running the Metro CBS (or atleast compiling) and I'm getting some build errors using both the Sep-24-09 nightly and the Dec-9-09 nightly build of metro. What version are you guys using? Anything else I should be aware of? This is my error: - [javac] D:\Stonehenge\stocktrader\metro\trader_client\src\org\apache\stonehenge\stocktrader\service\CookieManager.java:7: package com.sun.identity.wsfederation.client does not exist [javac] import com.sun.identity.wsfederation.client.WSFederationClient; [javac]^ [javac] D:\Stonehenge\stocktrader\metro\trader_client\src\org\apache\stonehenge\stocktrader\service\CookieManager.java:51: cannot find symbol [javac] symbol : variable WSFederationClient [javac] location: class org.apache.stonehenge.stocktrader.service.CookieManager [javac] String samlAssertion = WSFederationClient.getUserSAMLAssertion(java.net.URLEncoder.encode(assertionId), url, null, null); Thanks, -Ben Dewey
RE: WSO2 Testing
Chintana, I tested WSAS again and this time I'm getting the following message connecting to the active_sts: General security error (SAML token security failure); nested exception is: org.opensaml.MalformedException: Subject is invalid, requires either NameIdentifier or at least one ConfirmationMethod -Ben Dewey
RE: Installing Identity Server alongside (or on top of) WSAS
Input from Chintana would be great, but I did this by modifying the D:\wso2wsas-3.0\conf\transports.xml for WSAS to use 9764 and 9444 instead of (9763 and 9443). -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Monday, February 08, 2010 3:17 PM To: stonehenge-dev@incubator.apache.org Subject: Installing Identity Server alongside (or on top of) WSAS Hello, I have been able to use Identity Server as a passive STS successfully with all of the .NET components, and I was going to try to test out the WSAS services too. However, I realized that I would need WSAS as well. How can I install and run WSAS side-by-side with identity server? I can only seem to get one or the other working at any given moment. Thanks - Nick
Incubator February 2010 Status Report
Team, The February 2010 Status Report has been submitted to http://wiki.apache.org/incubator/February2010, please feel free to review and make any modification before the deadline of this Wed 10 Feb 2010. Thanks to Abu Obeida Bakhach for doing the leg work here. -Ben Dewey
Metro (sun-jaxws.xml) - Licensing question
In the metro build we are including configuration files for sun-jaxws.xml and web.xml. Both of the files contains (what appears to be boiler-plate) sun copyright on the top[1]. Does anyone know the source of this? Are these licenses required for using these XML files or are these just licenses that accidentally got copied over from another sample? AFAIK, these files will fail the apache licensing rules, if this license is required, is there any way to generate this file so that it's not included in the src? Thanks, Ben Dewey [1] !-- DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Copyright 1997-2008 Sun Microsystems, Inc. All rights reserved. The contents of this file are subject to the terms of either the GNU General Public License Version 2 only (GPL) or the Common Development and Distribution License(CDDL) (collectively, the License). You may not use this file except in compliance with the License. You can obtain a copy of the License at https://glassfish.dev.java.net/public/CDDL+GPL.html or glassfish/bootstrap/legal/LICENSE.txt. See the License for the specific language governing permissions and limitations under the License. When distributing the software, include this License Header Notice in each file and include the License file at glassfish/bootstrap/legal/LICENSE.txt. Sun designates this particular file as subject to the Classpath exception as provided by Sun in the GPL Version 2 section of the License file that accompanied this code. If applicable, add the following below the License Header, with the fields enclosed by brackets [] replaced by your own identifying information: Portions Copyrighted [year] [name of copyright owner] Contributor(s): If you wish your version of this file to be governed by only the CDDL or only the GPL Version 2, indicate your decision by adding [Contributor] elects to include this software in this distribution under the [CDDL or GPL Version 2] license. If you don't indicate a single choice of license, a recipient has the option to distribute your version of this file under either the CDDL, the GPL Version 2 or to extend the choice of license to its licensees as provided above. However, if you add GPL Version 2 code and therefore, elected the GPL Version 2 license, then the option applies only if the new code is made subject to such option by the copyright holder. --
RE: WSO2 Testing
Chintana, Thanks, I am out of the country and will test when I return next Monday. -Ben Dewey From: Chintana Wilamuna [chinta...@gmail.com] Sent: Monday, February 01, 2010 9:21 AM To: stonehenge-dev@incubator.apache.org Subject: Re: WSO2 Testing On Mon, Feb 1, 2010 at 3:21 PM, Chintana Wilamuna chinta...@gmail.com wrote: Like I said on a previous mail, I had to change the certificate to OPS.Com in the WSAS business service. I did not commit it since I'm not sure whether the change of certificate in the .Net trader client is deliberate. Ben, as Pablo explained on the other thread I changed the certificate to OPS.Com in the WSAS business service. Could you please build again after getting and update from the trunk please? Thanks, Bye, -Chintana -- Blog: http://engwar.com/ Photos: http://flickr.com/photos/chintana
Re: WSO2 Testing
I am using wsas3.0 - Ben Dewey -Original Message- Date: Wednesday, January 27, 2010 10:17:01 pm To: stonehenge-dev@incubator.apache.org From: Chintana Wilamuna chinta...@gmail.com Subject: Re: WSO2 Testing On Tue, Jan 26, 2010 at 8:14 AM, Ben Dewey ben.de...@26ny.com wrote: Do you have any idea why I'm receiving these errors? Â Has anyone else tested this? Â Are others experiencing these issues? Ben, What's the WSAS version you're using? Bye, -Chintana -- Blog: http://engwar.com/ Photos: http://flickr.com/photos/chintana
[jira] Updated: (STONEHENGE-4) Moving Framework independent code from contrib\stocktrader\java to trunk\stocktrader\java
[ https://issues.apache.org/jira/browse/STONEHENGE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey updated STONEHENGE-4: --- Fix Version/s: (was: M2) Moved off of M2 Release Moving Framework independent code from contrib\stocktrader\java to trunk\stocktrader\java - Key: STONEHENGE-4 URL: https://issues.apache.org/jira/browse/STONEHENGE-4 Project: Stonehenge Issue Type: Task Reporter: S.Uthaiyashankar Code available in https://svn.apache.org/repos/asf/incubator/stonehenge/contrib/stocktrader/java includes framework independent code as well as WSAS/Axis2 specific code. We have to identify framework independent code and move it to trunk\stocktrader\java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: WSO2 Testing
Ping Chintana,
Do you have any idea why I'm receiving these errors? Has anyone else tested
this? Are others experiencing these issues?
-Ben Dewey
From: Ben Dewey
Sent: Sunday, January 10, 2010 10:25 AM
To: stonehenge-dev@incubator.apache.org
Subject: WSO2 Testing
I’ve tested the following scenarios with the .NET and WSO2 Clients.
--
.NET Client - WSAS IS (Passive STS) - .NET Active STS - .NET BS – PASS (Had
to remove the requireSignatureConfirmation=false)
--
.NET Client - WSAS IS (Passive STS) - .NET Active STS - WSAS BS – Failed
[2010-01-10 10:15:44,853] INFO - org.apache.axis2.AxisFault: Error in
extracting message properties{org.apache.axis2.transport.http.AxisServlet}
[2010-01-10 10:16:46,659] ERROR - Must Understand check failed for header
http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd :
Security {org.apache.axis2.engine.AxisEngine}
See the WSAS_ActiveSTS_BS-Request.txt Attachment
Additionally, for the documentation I had to change the
wsas/conf/transports.xml to setup WSAS on a different port than WSIS.
.NET Client - .NET (Passive STS) - .NET Active STS - WSAS BS - Failed
[2010-01-10 10:15:44,853] INFO - org.apache.axis2.AxisFault: Error in
extracting message properties{org.apache.axis2.transport.http.AxisServlet}
[2010-01-10 10:16:46,659] ERROR - Must Understand check failed for header
http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd :
Security {org.apache.axis2.engine.AxisEngine}
[jira] Commented: (STONEHENGE-115) Provide OpenSSO metadata files for using OpenSSO IDP from .NET implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802272#action_12802272 ] Ben Dewey commented on STONEHENGE-115: -- Those were my intentions as well, but I used the filenames to do that. Can you check the filenames in the trunk and ensure this naming works? Provide OpenSSO metadata files for using OpenSSO IDP from .NET implementation - Key: STONEHENGE-115 URL: https://issues.apache.org/jira/browse/STONEHENGE-115 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: METRO Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: metadata.zip Some OpenSSO metadata files are missing for configuring the passive STS (OpenSSO IDP) in the .NET application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-116) Provide OpenSSO metada files for configuring .NET passive STS as SP
[ https://issues.apache.org/jira/browse/STONEHENGE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802273#action_12802273 ] Ben Dewey commented on STONEHENGE-116: -- Those were my intentions as well, but I used the filenames to do that. Can you check the filenames in the trunk and ensure this naming works? Provide OpenSSO metada files for configuring .NET passive STS as SP --- Key: STONEHENGE-116 URL: https://issues.apache.org/jira/browse/STONEHENGE-116 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: METRO Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: metadata.zip Some OpenSSO metadata files are missing for configuring the .NET passive STS as SP in OpenSSO. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-117) Update WCF bindings in .NET to use compatible security policies with Metro
[ https://issues.apache.org/jira/browse/STONEHENGE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802277#action_12802277 ] Ben Dewey commented on STONEHENGE-117: -- WSIS Implementation is under the WSAS folder and was committed by WSO2, its very easy to setup and instructions can be found here: http://www.mail-archive.com/stonehenge-dev@incubator.apache.org/msg02237.html You need to download WSIS from http://wso2.org/projects/identity Send any quesitons to the list and Chintana or myself can help. Update WCF bindings in .NET to use compatible security policies with Metro -- Key: STONEHENGE-117 URL: https://issues.apache.org/jira/browse/STONEHENGE-117 Project: Stonehenge Issue Type: Improvement Components: DOTNET_BS, DOTNET_CLIENT, DOTNET_OPS Affects Versions: M2 Environment: .NET Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: dotnet_interop.patch Update all the WCF bindings and configuration settings in the .NET implementation to use compatible security policies with Metro. Also make sure the latest WS-* spec versions are used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-115) Provide OpenSSO metadata files for using OpenSSO IDP from .NET implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802054#action_12802054 ] Ben Dewey commented on STONEHENGE-115: -- I tried to only commit the diffs for this patch. Please verify these changes and report any issues or close the ticket. Provide OpenSSO metadata files for using OpenSSO IDP from .NET implementation - Key: STONEHENGE-115 URL: https://issues.apache.org/jira/browse/STONEHENGE-115 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: METRO Reporter: Pablo Mariano Cibraro Attachments: metadata.zip Some OpenSSO metadata files are missing for configuring the passive STS (OpenSSO IDP) in the .NET application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Metro Interop Changes
Pablo, I made my best attempts to commit all your patches as is, but i did take some liberties. Please see the comments on the tickets and let me know if there is anything that needs to be resolved. Thanks for all your work and testing, Thank you Jiandong also. -Ben Dewey
[jira] Reopened: (STONEHENGE-70) Updated config code and settings to include Sun Metro services as target endpoints
[ https://issues.apache.org/jira/browse/STONEHENGE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey reopened STONEHENGE-70: - Reopening to refresh jira. Its still showing as unresolved on the status page. Will be resolved right away. Updated config code and settings to include Sun Metro services as target endpoints -- Key: STONEHENGE-70 URL: https://issues.apache.org/jira/browse/STONEHENGE-70 Project: Stonehenge Issue Type: Improvement Components: DOTNET_BS, DOTNET_CLIENT Affects Versions: M1 Reporter: Kent Brown Priority: Minor Fix For: M2 Attachments: Stonehenge-70-NEW.patch, Stonehenge-70.patch Original Estimate: 0.5h Remaining Estimate: 0.5h Extended the code and configuration options to make it easy to switch the .NET web applicaiton to call the Sun Metro Business Service and the .NET Business Service to call the Sun Metro Order Procesing Service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (STONEHENGE-115) Provide OpenSSO metadata files for using OpenSSO IDP from .NET implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey updated STONEHENGE-115: - Fix Version/s: M2 fixed in M2 Provide OpenSSO metadata files for using OpenSSO IDP from .NET implementation - Key: STONEHENGE-115 URL: https://issues.apache.org/jira/browse/STONEHENGE-115 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: METRO Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: metadata.zip Some OpenSSO metadata files are missing for configuring the passive STS (OpenSSO IDP) in the .NET application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (STONEHENGE-118) Update Metro service policies to use compatible policies with .NET
[ https://issues.apache.org/jira/browse/STONEHENGE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey updated STONEHENGE-118: - fixed in M2 Update Metro service policies to use compatible policies with .NET -- Key: STONEHENGE-118 URL: https://issues.apache.org/jira/browse/STONEHENGE-118 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: METRO Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: metro_interop.patch Update all the policies and configuration settings in the Metro implementation to use compatible security policies with .NET. Also make sure the latest WS-* spec versions are used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-111) .NET Trader isn't using the userId claim returned from the ActiveSTS
[ https://issues.apache.org/jira/browse/STONEHENGE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-111. -- Resolution: Fixed Fix Version/s: M2 This issue has been resolved with STONEHENEGE-117 .NET Trader isn't using the userId claim returned from the ActiveSTS Key: STONEHENGE-111 URL: https://issues.apache.org/jira/browse/STONEHENGE-111 Project: Stonehenge Issue Type: Bug Components: DOTNET_CLIENT Affects Versions: M2 Environment: dotnet Reporter: Ben Dewey Fix For: M2 Attachments: UserIdClaim.patch, UserIdClaim.patch I can't seem to find anywhere that the TraderClient is using the userid returned from the active STS. There are two places I've seen. 1. Account.aspx.cs (line 40): userid is set to null and the GetDefaultUserId is used 2. Controls/AccountOrders.ascx.cs (line 46): userId is set to HttpContext.Current.User.Identity.Name which returns unll The should both be something like the following: userid = (from c in ((IClaimsIdentity)HttpContext.Current.User.Identity).Claims where c.ClaimType == http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier; select c.Value).FirstOrDefault(); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: WSO2 Testing
Ping Chintana,
I should have some time this weekend to do some more testing. Do you know why
I'm receiving these errors?
Thanks,
-Ben Dewey
-Original Message-
From: Ben Dewey [mailto:ben.de...@26ny.com]
Sent: Sunday, January 10, 2010 10:25 AM
To: stonehenge-dev@incubator.apache.org
Subject: WSO2 Testing
I've tested the following scenarios with the .NET and WSO2 Clients.
--
.NET Client - WSAS IS (Passive STS) - .NET Active STS - .NET BS - PASS (Had
to remove the requireSignatureConfirmation=false)
--
.NET Client - WSAS IS (Passive STS) - .NET Active STS - WSAS BS - Failed
[2010-01-10 10:15:44,853] INFO - org.apache.axis2.AxisFault: Error in
extracting message properties{org.apache.axis2.transport.http.AxisServlet}
[2010-01-10 10:16:46,659] ERROR - Must Understand check failed for header
http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd :
Security {org.apache.axis2.engine.AxisEngine}
See the WSAS_ActiveSTS_BS-Request.txt Attachment
Additionally, for the documentation I had to change the
wsas/conf/transports.xml to setup WSAS on a different port than WSIS.
.NET Client - .NET (Passive STS) - .NET Active STS - WSAS BS - Failed
[2010-01-10 10:15:44,853] INFO - org.apache.axis2.AxisFault: Error in
extracting message properties{org.apache.axis2.transport.http.AxisServlet}
[2010-01-10 10:16:46,659] ERROR - Must Understand check failed for header
http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd :
Security {org.apache.axis2.engine.AxisEngine}
RE: Configuring .Net client to talk to Identity Server passive STS
Ben, just added the cert to stocktrader svn/wsas/identity/resources. Thanks, I'll try it now -Ben Dewey
WSO2 Testing
I've tested the following scenarios with the .NET and WSO2 Clients.
--
.NET Client - WSAS IS (Passive STS) - .NET Active STS - .NET BS - PASS (Had
to remove the requireSignatureConfirmation=false)
--
.NET Client - WSAS IS (Passive STS) - .NET Active STS - WSAS BS - Failed
[2010-01-10 10:15:44,853] INFO - org.apache.axis2.AxisFault: Error in
extracting message properties{org.apache.axis2.transport.http.AxisServlet}
[2010-01-10 10:16:46,659] ERROR - Must Understand check failed for header
http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd :
Security {org.apache.axis2.engine.AxisEngine}
See the WSAS_ActiveSTS_BS-Request.txt Attachment
Additionally, for the documentation I had to change the
wsas/conf/transports.xml to setup WSAS on a different port than WSIS.
.NET Client - .NET (Passive STS) - .NET Active STS - WSAS BS - Failed
[2010-01-10 10:15:44,853] INFO - org.apache.axis2.AxisFault: Error in
extracting message properties{org.apache.axis2.transport.http.AxisServlet}
[2010-01-10 10:16:46,659] ERROR - Must Understand check failed for header
http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd :
Security {org.apache.axis2.engine.AxisEngine}
POST /services/TradeServiceWsas HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: getAccountData
Host: localhost:9765
Content-Length: 15538
Expect: 100-continue
Connection: Keep-Alive
s:Envelope xmlns:s=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:a=http://www.w3.org/2005/08/addressing;
xmlns:u=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;s:Headera:Action
s:mustUnderstand=1 u:Id=_5getAccountData/a:Actiona:MessageID
u:Id=_6urn:uuid:dcf00d21-fdd3-4ed9-a9ae-a765d12d89c2/a:MessageIDa:ReplyTo
u:Id=_7a:Addresshttp://www.w3.org/2005/08/addressing/anonymous/a:Address/a:ReplyToa:To
s:mustUnderstand=1
u:Id=_8http://localhost:9765/services/TradeServiceWsas/a:Too:Security
s:mustUnderstand=1
xmlns:o=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;u:Timestamp
u:Id=uuid-c534be05-dc9d-4355-ae3b-3cc1a5b56e1c-16u:Created2010-01-10T15:15:41.853Z/u:Createdu:Expires2010-01-10T15:20:41.853Z/u:Expires/u:Timestampe:EncryptedKey
Id=uuid-c534be05-dc9d-4355-ae3b-3cc1a5b56e1c-15
xmlns:e=http://www.w3.org/2001/04/xmlenc#;e:EncryptionMethod
Algorithm=http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p;DigestMethod
Algorithm=http://www.w3.org/2000/09/xmldsig#sha1;
xmlns=http://www.w3.org/2000/09/xmldsig#//e:EncryptionMethodKeyInfo
xmlns=http://www.w3.org/2000/09/xmldsig#;o:SecurityTokenReferenceo:KeyIdentifier
ValueType=http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1;+g9Yu2BfpDNp4nno+QiIcv3gmUM=/o:KeyIdentifier/o:SecurityTokenReference/KeyInfoe:CipherDatae:CipherValueF8QctbMekHlkmLmlVuYVBTDrvQQMIboEOSaFPb8rsHFsqacMKr5sciqZ3i4uT612q4fP30VK1fRiSt1cwLEA8J1W7cDDdU0x5t7eN6GD3x8LfU5JXugmSJFesrL22WgoeTPz0oS7g8LWhu1d5pODs+3cOkMUv364+QpSyVemguk=/e:CipherValue/e:CipherData/e:EncryptedKeysc:DerivedKeyToken
u:Id=_0
xmlns:sc=http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512;o:SecurityTokenReferenceo:Reference
URI=#uuid-c534be05-dc9d-4355-ae3b-3cc1a5b56e1c-15//o:SecurityTokenReferencesc:Offset0/sc:Offsetsc:Length24/sc:Lengthsc:NonceFBQMYMDVoC0dR/iD6eJTWQ==/sc:Nonce/sc:DerivedKeyTokensc:DerivedKeyToken
u:Id=_2
xmlns:sc=http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512;o:SecurityTokenReferenceo:Reference
URI=#uuid-c534be05-dc9d-4355-ae3b-3cc1a5b56e1c-15//o:SecurityTokenReferencesc:NonceHhqMF+2gpxMNHnEMZ+qbpw==/sc:Nonce/sc:DerivedKeyTokene:ReferenceList
xmlns:e=http://www.w3.org/2001/04/xmlenc#;e:DataReference
URI=#_4/e:DataReference URI=#_10/e:DataReference
URI=#_11//e:ReferenceListxenc:EncryptedData
Type=http://www.w3.org/2001/04/xmlenc#Element;
xmlns:xenc=http://www.w3.org/2001/04/xmlenc#;xenc:EncryptionMethod
Algorithm=http://www.w3.org/2001/04/xmlenc#aes256-cbc;/xenc:EncryptionMethodKeyInfo
xmlns=http://www.w3.org/2000/09/xmldsig#;e:EncryptedKey
xmlns:e=http://www.w3.org/2001/04/xmlenc#;e:EncryptionMethod
Algorithm=http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p;DigestMethod
WSAS BS STS Testing
Chintana,
When I use the WSAS BS with the .NET Client I get a 500 Error. The WSAS log
reports an error:
Any thoughts? Please let me know if there is more information that you need
from me.
---
[2010-01-07 22:26:30,983] ERROR - Must Understand check failed for header http:
//docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : S
ecurity {org.apache.axis2.engine.AxisEngine}
org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.
oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security
at org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.jav
a:102)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReq
uest(HTTPTransportUtils.java:275)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:1
33)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleR
equest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(P
roxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyS
ervlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:210)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:151)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:870)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:685)
at java.lang.Thread.run(Thread.java:619)
[2010-01-07 22:26:31,035] INFO - org.apache.axis2.AxisFault: Error in extracti
ng message properties {org.apache.axis2.transport.http.AxisServlet}
RE: Configuring .Net client to talk to Identity Server passive STS
Chintana, 3) Add the Identity Server certificate to the certificate store using MMC. I've attached the cert with this mail, localhost.crt. Will put this into SVN also. I'm not able to find the localhost.crt file anywhere. Is it in SVN anywhere? Can you add it? Thanks, Ben Dewey
RE: Configuring .Net client to talk to Identity Server passive STS
I was able to get the .NET Client communication and authenticating successfully with WSO2IS. I'm getting a certificate message, 'The certificate that was used has a trust chain that cannot be verified'. Once I get the cert installed I should be good to go. Thanks, Ben Dewey -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Thursday, January 07, 2010 10:50 PM To: stonehenge-dev@incubator.apache.org Subject: RE: Configuring .Net client to talk to Identity Server passive STS Chintana, 3) Add the Identity Server certificate to the certificate store using MMC. I've attached the cert with this mail, localhost.crt. Will put this into SVN also. I'm not able to find the localhost.crt file anywhere. Is it in SVN anywhere? Can you add it? Thanks, Ben Dewey
RE: Unresolved JIRA Tickets
Chintana, Is it okay if I change STONEHENGE-8 and STONEHENGE-74 to Unscheduled? Are you expecting these to be included in the M2 release? -Ben Dewey https://issues.apache.org/jira/browse/STONEHENGE-8 https://issues.apache.org/jira/browse/STONEHENGE-74 -Original Message- From: Kent Brown [mailto:kent.br...@microsoft.com] Sent: Monday, January 04, 2010 5:52 PM To: stonehenge-dev@incubator.apache.org Subject: RE: Unresolved JIRA Tickets Ben, Looks like you got pretty good response to this. Can everyone (Ben, Pablo, Jiandong, Nick, Chintana, etc.) please respond by email (or new JIRA tickets) a summary of all the open issues (you own or from other parties that affect you) that would prevent us from doing a release? Kent Brown -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Tuesday, December 15, 2009 8:01 PM To: stonehenge-dev@incubator.apache.org Subject: Unresolved JIRA Tickets All, There are numerous unresolved issues in JIRA at the moment. As we are approaching the M2 release these issues are making it difficult to judge our status. Please take this time to update any JIRA tickets and resolve any issues. If I don't hear any update in the next 48 hrs I'll start resolving any issues that have been committed. Thanks, -Ben Dewey
[jira] Updated: (STONEHENGE-8) Perl client for StockTrader
[ https://issues.apache.org/jira/browse/STONEHENGE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey updated STONEHENGE-8: --- Fix Version/s: (was: M2) moved to Unspecified Perl client for StockTrader --- Key: STONEHENGE-8 URL: https://issues.apache.org/jira/browse/STONEHENGE-8 Project: Stonehenge Issue Type: Task Environment: Linux. Reporter: Chintana Wilamuna Attachments: StockTrader.tar.gz Trader client using WSF/Perl and Catalyst. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (STONEHENGE-74) OpenID login for PHP client
[ https://issues.apache.org/jira/browse/STONEHENGE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey updated STONEHENGE-74: Fix Version/s: (was: M2) Moved to Unspecified OpenID login for PHP client --- Key: STONEHENGE-74 URL: https://issues.apache.org/jira/browse/STONEHENGE-74 Project: Stonehenge Issue Type: New Feature Components: PHP_CLIENT Environment: PHP Reporter: Chintana Wilamuna Priority: Minor Attachments: login.php.patch, openid.patch, openid.png As part of the effort of moving to claims based security - https://issues.apache.org/jira/browse/STONEHENGE-73, add OpenID login for Stonehenge PHP client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (STONEHENGE-15) Protect connection strings in Business Services and Order Processor solutions
[ https://issues.apache.org/jira/browse/STONEHENGE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey closed STONEHENGE-15. --- Resolution: Won't Fix Based on scott's previous email, we've decided not to fix this issue Protect connection strings in Business Services and Order Processor solutions - Key: STONEHENGE-15 URL: https://issues.apache.org/jira/browse/STONEHENGE-15 Project: Stonehenge Issue Type: Improvement Components: DOTNET_BS, DOTNET_OPS Environment: .NET trunk Reporter: Scott Golightly Assignee: Scott Golightly Priority: Minor Fix For: M2 Original Estimate: 2h Remaining Estimate: 2h The database connection strings are listed in plain text in the configuration files. .NET provides the means to encrypt the connection strings and automatically decrypt the values before using it. Encrypting the connection string is a best practice to protect the database login information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-21) Having a unified configuration system
[ https://issues.apache.org/jira/browse/STONEHENGE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-21. - Resolution: Fixed This issue was fixed in the 1.1 tag. All new implementation contain a consistent Config Service and Config tab on the UI Having a unified configuration system - Key: STONEHENGE-21 URL: https://issues.apache.org/jira/browse/STONEHENGE-21 Project: Stonehenge Issue Type: New Feature Reporter: S.Uthaiyashankar Fix For: M2 Attachments: ConfigContract.patch, StockTrader Configuration Specification_v3.doc Currently, .NET Services and PHP/WSAS Services are configured differently. .NET uses file based configuration and PHP/WSAS uses database configurations. We have to find a common mechanism to store the configurations. One option is to have a configuration service and then all the other services request endpoint details from configuration service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (STONEHENGE-52) Change hosting provider for the .NET BS and OPS
[ https://issues.apache.org/jira/browse/STONEHENGE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey closed STONEHENGE-52. --- Resolution: Won't Fix For now we are going to leave the dotnet services as the self-hosted console applications. Change hosting provider for the .NET BS and OPS --- Key: STONEHENGE-52 URL: https://issues.apache.org/jira/browse/STONEHENGE-52 Project: Stonehenge Issue Type: Improvement Components: DOTNET_BS, DOTNET_OPS Reporter: Ben Dewey Fix For: M2 There has been discussions on the list about moving the .NET BS and OPS services into a different hosting provider. The plan is still up for discussion. We are currently evaluating: 1. Leaving it as a console hosted service 2. Hosting the services in IIS 3. Hosting the services as a Windows Service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-70) Updated config code and settings to include Sun Metro services as target endpoints
[ https://issues.apache.org/jira/browse/STONEHENGE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-70. - Resolution: Fixed This issue was fixed in the 1.1 tag when metro was committed to the trunk. Updated config code and settings to include Sun Metro services as target endpoints -- Key: STONEHENGE-70 URL: https://issues.apache.org/jira/browse/STONEHENGE-70 Project: Stonehenge Issue Type: Improvement Components: DOTNET_BS, DOTNET_CLIENT Affects Versions: M1 Reporter: Kent Brown Priority: Minor Fix For: M2 Attachments: Stonehenge-70-NEW.patch, Stonehenge-70.patch Original Estimate: 0.5h Remaining Estimate: 0.5h Extended the code and configuration options to make it easy to switch the .NET web applicaiton to call the Sun Metro Business Service and the .NET Business Service to call the Sun Metro Order Procesing Service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-59) Incorrect creation date when order processor service is down
[ https://issues.apache.org/jira/browse/STONEHENGE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-59. - Resolution: Fixed Chintana, I tested this again and it seems to be working, so I'm resolving it. Incorrect creation date when order processor service is down Key: STONEHENGE-59 URL: https://issues.apache.org/jira/browse/STONEHENGE-59 Project: Stonehenge Issue Type: Bug Environment: Windows XP Reporter: Chintana Wilamuna Fix For: M2 Steps to reproduce. 1) Start .Net order processor service 2) Configure the database such that PHP_CLIENT - PHP_BS - DOTNET_OPS 3) Login and click 'Quotes/Trade' 4) Click on an item to 'Buy' it. 5) Close the .Net order processor service 6) Click the 'Buy' button to buy the number of shares you want Creation date column is having an incorrect date. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-78) Add a footer to the .NET and PHP Clients that display the current config
[ https://issues.apache.org/jira/browse/STONEHENGE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-78. - Resolution: Fixed The footer has been added to the .NET Client Add a footer to the .NET and PHP Clients that display the current config Key: STONEHENGE-78 URL: https://issues.apache.org/jira/browse/STONEHENGE-78 Project: Stonehenge Issue Type: Improvement Components: DOTNET_CLIENT, PHP_CLIENT Reporter: Ben Dewey Assignee: Nicholas A Hauenstein Fix For: M2 Attachments: STONEHENGE-78.zip I was giving the interop demo in front of a live audience tonight and we felt that it would be a nice feature to include the current configuration in the footer of the .net and php client. Pros: - You can refresh and quickly see at a glance how the configuration is setup Cons: - Doesn't fit into the design, (although were demonstrating function not design) - Requires an extra calls to the config service - Creates a dependency from trade client to GetBSConfig I think the pro out weighs the con. Any thoughts? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-90) Update of the Metro version of StockTrader
[ https://issues.apache.org/jira/browse/STONEHENGE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-90. - Resolution: Fixed Metro has been committed to the trunk and is included in the 1.1 tag Update of the Metro version of StockTrader -- Key: STONEHENGE-90 URL: https://issues.apache.org/jira/browse/STONEHENGE-90 Project: Stonehenge Issue Type: New Feature Affects Versions: M1, M2 Environment: jdk6, metro2.0 nightly build on 0706, glassfish 2.1, wsdl from the latest .net version of Config Service Reporter: Ming Jin Fix For: M2 Attachments: Metro_Patch20090722.patch, MetroDeploy_Troubleshoot_Walkthru.doc, MetroWithJSFUIAndBasicConfigService.zip We've done several tasks in the Metro version of StockTrader, and got them approved from Kent and Harold. Now we think it's ready to provide a patch file for the community to update the application in repository so that the metro version can be moved from the contrib to the trunk. The tasks contain: 1. clean up the namespace of java code to 'org.apache.stonehenge.stocktrader' 2. provide a JSF based UI client (compatible with the .net version and the php version) 3. verify the interoperability among the versions of .net/php/wso2/metro using .net/java/php UI 4. delete all dependent jar files in the repo, and provide a instruction document 5. provide a Java Config Service which implements the basic functionality in the unified configuration proposal based on the wsdl of .net config service 6. verify the interoperability between .net config service and java config service 7. clean up the build scripts and restructure the project We attached the patch file including the above tasks in this issue. To do it, you need to apply the patch under the directory /contrib/stocktrader/metro, and choose 'apply all'. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-104) Upgrade all the existing WCF bindings to use the latest specs
[ https://issues.apache.org/jira/browse/STONEHENGE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792957#action_12792957 ] Ben Dewey commented on STONEHENGE-104: -- Pablo, What's the status of this patch. Does this need to be committed. Upgrade all the existing WCF bindings to use the latest specs -- Key: STONEHENGE-104 URL: https://issues.apache.org/jira/browse/STONEHENGE-104 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: DOTNET Reporter: Pablo Mariano Cibraro Fix For: M2 Attachments: latest_specs.patch Upgrade all the existing WCF bindings to use the latest specs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-93) Advanced Java Configuration User Interface
[ https://issues.apache.org/jira/browse/STONEHENGE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-93. - Resolution: Fixed The advance configuration service was added as part of the CBS Implementation of Metro Advanced Java Configuration User Interface -- Key: STONEHENGE-93 URL: https://issues.apache.org/jira/browse/STONEHENGE-93 Project: Stonehenge Issue Type: New Feature Affects Versions: M2 Reporter: Ming Jin Fix For: M2 add advanced config service in Java like the .NET version -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-69) Initial Metro-based version of StockTrader sample application
[ https://issues.apache.org/jira/browse/STONEHENGE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-69. - Resolution: Fixed Fix Version/s: M2 The StockTrader Metro implementation has been added to the trunk Initial Metro-based version of StockTrader sample application - Key: STONEHENGE-69 URL: https://issues.apache.org/jira/browse/STONEHENGE-69 Project: Stonehenge Issue Type: New Feature Environment: Metro 1.5 GlassFish 2.1 JDK 6 Reporter: Harold Carr Fix For: M2 Attachments: metroaa, metroab, metroac, metroad This is the initial submission of a Metro-based version of the StockTrader sample application. It works, both clear and secure, with the .NET version. It has not been tested with other versions yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STONEHENGE-73) Change Stonehenge to use claims based security
[ https://issues.apache.org/jira/browse/STONEHENGE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey resolved STONEHENGE-73. - Resolution: Fixed Fix Version/s: M2 The CBS Implementation of .NET has been added to the trunk Change Stonehenge to use claims based security -- Key: STONEHENGE-73 URL: https://issues.apache.org/jira/browse/STONEHENGE-73 Project: Stonehenge Issue Type: New Feature Components: Documentation, DOTNET_BS, DOTNET_CLIENT, DOTNET_OPS, PHP_BS, PHP_CLIENT, PHP_OPS, WSAS_BS, WSAS_OPS Affects Versions: M2 Environment: All of the Stonehenge stock trader applications Reporter: Scott Golightly Assignee: Scott Golightly Fix For: M2 Attachments: Changes to Apache Stonehenge to Support Claims Based Security.docx, Changes to Apache Stonehenge to Support Claims Based Security.docx, Changes to Apache Stonehenge to Support Claims Based Security.pdf, Changes to Apache Stonehenge to Support Claims Based Security.pdf, StonehengeIdentity-02-Sep-2009.zip, StonehengeIdentity-08-Aug-2009.zip, stonehengeIdentity-08-Oct-2009.zip I am proposing that we change the authentication and authorization mechanism in Stonehenge to use claims based tokens rather than the current user name/password. I am attaching a word document and a .PDF of the document that explains in greater detail the proposal. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (STONEHENGE-89) PHP, METRO and .NET ConfigService Interoperability
[ https://issues.apache.org/jira/browse/STONEHENGE-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Dewey closed STONEHENGE-89. --- Resolution: Duplicate This issue is a duplicate of STONEHENGE-98 PHP, METRO and .NET ConfigService Interoperability -- Key: STONEHENGE-89 URL: https://issues.apache.org/jira/browse/STONEHENGE-89 Project: Stonehenge Issue Type: Wish Reporter: Avantika Agrawal It would be nice if we could reconcile the differences between the two config services so that we can test interoperability between them. Ben and I have been working on testing this - he can probably provide more details on the test results. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-109) WIF RC Support for .NET Implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791172#action_12791172 ] Ben Dewey commented on STONEHENGE-109: -- Pablo, Please resolve this ticket if everything looks okay, Let me know if you have any problems. WIF RC Support for .NET Implementation -- Key: STONEHENGE-109 URL: https://issues.apache.org/jira/browse/STONEHENGE-109 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: .NET Reporter: Pablo Mariano Cibraro Attachments: wif_rc.patch I migrated all the existing code to use WIF RC. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Unresolved JIRA Tickets
All, There are numerous unresolved issues in JIRA at the moment. As we are approaching the M2 release these issues are making it difficult to judge our status. Please take this time to update any JIRA tickets and resolve any issues. If I don't hear any update in the next 48 hrs I'll start resolving any issues that have been committed. Thanks, -Ben Dewey
RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned from the ActiveSTS
Pablo, Could you apply it in the trunk when you have some time ?. I'll try to get around to it this weekend, but I'm going out-of-town, so if not I should be able to apply it on Monday night. Although, I just looked at the patch and have one question. It seems you are checking to see if GetUserIdClaim() == null, but the final line in that function throws an exception. Doesn't seem like that would work, am I reading that wrong? -Ben Dewey
RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned from the ActiveSTS
Pablo,
My concern was that 'throw new Exception(The profile id claim was not provided
by the Active STS);' (inside of GetUserIdClaim()) would get called if no claim
exists and all the service implementation code would get faulted.
-Ben Dewey
-Original Message-
From: Pablo Cibraro [mailto:pablo.cibr...@tellago.com]
Sent: Friday, December 11, 2009 2:04 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned
from the ActiveSTS
No problem Ben. This is the code I am using,
string userClaim = GetUserIdClaim();
if (userClaim != null)
{
userID = userClaim;
}
I am basically looking for the user id in the claims. If the claim is not
found, the userID is not set, so the userID passed as argument in the operation
is used. Otherwise, the user id in the claim is used. Does it make sense ?
Thanks
Pablo.
-Original Message-
From: Ben Dewey [mailto:ben.de...@26ny.com]
Sent: Friday, December 11, 2009 3:55 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned
from the ActiveSTS
Pablo,
Could you apply it in the trunk when you have some time ?.
I'll try to get around to it this weekend, but I'm going out-of-town, so if not
I should be able to apply it on Monday night.
Although, I just looked at the patch and have one question. It seems you are
checking to see if GetUserIdClaim() == null, but the final line in that
function throws an exception. Doesn't seem like that would work, am I reading
that wrong?
-Ben Dewey
RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned from the ActiveSTS
If we return null instead of throwing an exception does that mean that PHP and
the non-CBS implementation can call the BS the old way and still work as
expected? If so, yes.
-Ben Dewey
-Original Message-
From: Pablo Cibraro [mailto:pablo.cibr...@tellago.com]
Sent: Friday, December 11, 2009 2:31 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned
from the ActiveSTS
Oh, yes. You are right about that. Metro and .NET are both providing the user
id claim in the saml token, as it should be a requirement for executing the
business service. Shall we make that optional, and remove that line that throws
the exception ?
Thanks
Pablo.
-Original Message-
From: Ben Dewey [mailto:ben.de...@26ny.com]
Sent: Friday, December 11, 2009 4:22 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned
from the ActiveSTS
Pablo,
My concern was that 'throw new Exception(The profile id claim was not provided
by the Active STS);' (inside of GetUserIdClaim()) would get called if no claim
exists and all the service implementation code would get faulted.
-Ben Dewey
-Original Message-
From: Pablo Cibraro [mailto:pablo.cibr...@tellago.com]
Sent: Friday, December 11, 2009 2:04 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned
from the ActiveSTS
No problem Ben. This is the code I am using,
string userClaim = GetUserIdClaim();
if (userClaim != null)
{
userID = userClaim;
}
I am basically looking for the user id in the claims. If the claim is not
found, the userID is not set, so the userID passed as argument in the operation
is used. Otherwise, the user id in the claim is used. Does it make sense ?
Thanks
Pablo.
-Original Message-
From: Ben Dewey [mailto:ben.de...@26ny.com]
Sent: Friday, December 11, 2009 3:55 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: (STONEHENGE-111) .NET Trader isn't using the userId claim returned
from the ActiveSTS
Pablo,
Could you apply it in the trunk when you have some time ?.
I'll try to get around to it this weekend, but I'm going out-of-town, so if not
I should be able to apply it on Monday night.
Although, I just looked at the patch and have one question. It seems you are
checking to see if GetUserIdClaim() == null, but the final line in that
function throws an exception. Doesn't seem like that would work, am I reading
that wrong?
-Ben Dewey
RE: StockTrader Sample Documentation Updates
Nick Wrote: Those statements were based off the diagram at the bottom of the second page of the spec attached to STONEHENGE-73 [1]. Am I misreading that? I'd like to have Pablo's take on it. Is the scenario setup for a Brokerage Firms Web Site/Services and a Bank PassiveSTS? Seems to me that the diagram on p2 of [1] is incorrect, the website should be part of the brokerage firm. -Ben Dewey [1] http://issues.apache.org/jira/secure/attachment/12412416/Changes+to+Apache+Stonehenge+to+Support+Claims+Based+Security.pdf
RE: StockTrader Sample Documentation Updates
Additionally, In the diagram and ToC you mention ActiveSTS before PassiveSTS. Is that just for alphabetical reasons? Seems to me that PassiveSTS would come before ActiveSTS. The rationale being that ActiveSTS wouldn't exist without a token from the Passive and that PassiveSTS needs to process the users creds before the ActiveSTS can process the token retrieved from the PassiveSTS. Same is also kind of true for the BS v. ConfigService Scenario. Sorry if this is too nit-picky, just something to think about. -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Tuesday, December 08, 2009 7:24 PM To: stonehenge-dev@incubator.apache.org Subject: StockTrader Sample Documentation Updates Hello All, I took a stab at beginning documentation work for the StockTrader sample application. I am not a great scholar of claims-based security so if anyone would like to review and possibly edit/delete what is there, go right ahead. The main pages I touched were the following (and their respective children): http://cwiki.apache.org/confluence/display/STONEHENGE/Stonehenge+StockTrader+Sample+Application http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Client http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Business+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Configuration+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Order+Processor+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Database If either of the main diagrams will require update, let me know and I can tweak them. Also, I'm holding off on creating the pages for the Active STS and Passive STS until everything is in working order and the precise requirements for each are known and well defined. - Nick
RE: StockTrader Sample Documentation Updates
my own motivation for including 2 separate diagrams Fair enough, maybe after the Active/Passive Documentation is written it will shed more light on this. -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Thursday, December 10, 2009 12:24 PM To: stonehenge-dev@incubator.apache.org Subject: RE: StockTrader Sample Documentation Updates Is that just for alphabetical reasons? Correct. The concerns you mention are my own motivation for including 2 separate diagrams. The first one is more a categorization of components, with a little logical ordering of the categories. I struggled with the categorization of the Configuration Service, as it's more an infrastructure service unrelated to the application logic. On the other hand, I didn't want to throw everything into its own category either, as that would defeat the purpose of categorization. With that diagram and text I'm 100% open to complete overhaul with whatever best helps in understanding, and at the same time reflects what is actually present in the application. - Nick -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Thursday, December 10, 2009 9:17 AM To: stonehenge-dev@incubator.apache.org Subject: RE: StockTrader Sample Documentation Updates Additionally, In the diagram and ToC you mention ActiveSTS before PassiveSTS. Is that just for alphabetical reasons? Seems to me that PassiveSTS would come before ActiveSTS. The rationale being that ActiveSTS wouldn't exist without a token from the Passive and that PassiveSTS needs to process the users creds before the ActiveSTS can process the token retrieved from the PassiveSTS. Same is also kind of true for the BS v. ConfigService Scenario. Sorry if this is too nit-picky, just something to think about. -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Tuesday, December 08, 2009 7:24 PM To: stonehenge-dev@incubator.apache.org Subject: StockTrader Sample Documentation Updates Hello All, I took a stab at beginning documentation work for the StockTrader sample application. I am not a great scholar of claims-based security so if anyone would like to review and possibly edit/delete what is there, go right ahead. The main pages I touched were the following (and their respective children): http://cwiki.apache.org/confluence/display/STONEHENGE/Stonehenge+StockTrader+Sample+Application http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Client http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Business+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Configuration+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Order+Processor+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Database If either of the main diagrams will require update, let me know and I can tweak them. Also, I'm holding off on creating the pages for the Active STS and Passive STS until everything is in working order and the precise requirements for each are known and well defined. - Nick
RE: StockTrader Sample Documentation Updates
Regarding the second diagram, Again I think it looks great. The User icon (although its already pretty obvious) could have a label like the others. Also, I'm not sure the little arrows between client/passive STS are descriptive. AFAIK, the User communicates with the TraderClient/Passive STS independently and there is no actually communication between the TraderClient and the Passive STS. I'm not sure if this was the metaphor you were going with, but this may be a stumbling point for users. No need to change this, I'm just curious about others thoughts on this. -Ben Dewey
RE: StockTrader Sample Documentation Updates
Looks great. -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Thursday, December 10, 2009 12:59 PM To: stonehenge-dev@incubator.apache.org Subject: RE: StockTrader Sample Documentation Updates The User icon (although its already pretty obvious) could have a label like the others. Whoops! That is now fixed. AFAIK, the User communicates with the TraderClient/Passive STS independently and there is no actually communication between the TraderClient and the Passive STS. This is true. I'm torn on that one. I decided to use different arrows. The browser is technically doing the communication, but the location header that does the redirect and the action for the POSTed form are controlled by the Client and Passive STS respectively. As a trade-off I used a different arrows for this communication. As an edit (just updated), I changed the color to make the communicator more clear. - Nick Hauenstein -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Thursday, December 10, 2009 9:49 AM To: stonehenge-dev@incubator.apache.org Subject: RE: StockTrader Sample Documentation Updates Regarding the second diagram, Again I think it looks great. The User icon (although its already pretty obvious) could have a label like the others. Also, I'm not sure the little arrows between client/passive STS are descriptive. AFAIK, the User communicates with the TraderClient/Passive STS independently and there is no actually communication between the TraderClient and the Passive STS. I'm not sure if this was the metaphor you were going with, but this may be a stumbling point for users. No need to change this, I'm just curious about others thoughts on this. -Ben Dewey
RE: StockTrader Sample Documentation Updates
Another piece of great work Nick, Thanks. -Ben Dewey -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Thursday, December 10, 2009 3:27 PM To: stonehenge-dev@incubator.apache.org Subject: RE: StockTrader Sample Documentation Updates Thanks! I completed and added the final diagram (a swim lane diagram of the actual process described). I also updated the descriptions so that it is the stock broker that manages the Trader Client web app. - Nick -Original Message- From: Pablo Cibraro [mailto:pablo.cibr...@tellago.com] Sent: Thursday, December 10, 2009 10:46 AM To: stonehenge-dev@incubator.apache.org Subject: RE: StockTrader Sample Documentation Updates Excellent work Nick!!!. We were definitely needing this. Pablo.
[jira] Created: (STONEHENGE-111) .NET Trader isn't using the userId claim returned from the ActiveSTS
.NET Trader isn't using the userId claim returned from the ActiveSTS Key: STONEHENGE-111 URL: https://issues.apache.org/jira/browse/STONEHENGE-111 Project: Stonehenge Issue Type: Bug Components: DOTNET_CLIENT Affects Versions: M2 Environment: dotnet Reporter: Ben Dewey I can't seem to find anywhere that the TraderClient is using the userid returned from the active STS. There are two places I've seen. 1. Account.aspx.cs (line 40): userid is set to null and the GetDefaultUserId is used 2. Controls/AccountOrders.ascx.cs (line 46): userId is set to HttpContext.Current.User.Identity.Name which returns unll The should both be something like the following: userid = (from c in ((IClaimsIdentity)HttpContext.Current.User.Identity).Claims where c.ClaimType == http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier; select c.Value).FirstOrDefault(); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Using WSF with PHP 5.3 (was: Dead Link: PHP MSSQL Driver)
Chintana, I found this https://wso2.org/jira/browse/WSFPHP-400 related to compatibility of WSF with PHP 5.3, is this the best thing to watch regarding the status of this? But in terms of using ST Do I have to use PHP 5.2? -Ben Dewey -Original Message- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Wednesday, December 09, 2009 10:28 AM To: stonehenge-dev@incubator.apache.org Subject: Using WSF with PHP 5.3 (was: Dead Link: PHP MSSQL Driver) Chintana, I was able to get the SQL Server driver installed successfully with PHP 5.3, but I'm getting errors loading the WSF driver. Does WSF work with PHP 5.3? Error: -- PHP Warning: PHP Startup: wsf: Unable to initialize module\nModule compiled with module API=20060613\nPHPcompiled with module API=20090626\nThese options need to match\n in Unknown on line 0 Thanks, -Ben Dewey -Original Message- From: Chintana Wilamuna [mailto:chinta...@gmail.com] Sent: Tuesday, December 08, 2009 4:49 AM To: stonehenge-dev@incubator.apache.org Subject: Re: Dead Link: PHP MSSQL Driver On Tue, Dec 8, 2009 at 4:25 AM, Ben Dewey ben.de...@26ny.com wrote: The PHP MSSQL Driver is a dead link on the PHP documentation. Do you or Chintana have an updated link for this? Ben, The extension we were using has been discontinued from PHP 5.3. I just updated PHP stuff to use the latest MSSQL driver from Microsoft. Could you please take an svn up and try? The new driver location is - http://www.microsoft.com/downloads/details.aspx?displaylang=enFamilyID=ccdf728b-1ea0-48a8-a84a-5052214caad9 Bye, -Chintana -- http://engwar.com/
[jira] Issue Comment Edited: (STONEHENGE-110) DAL assembly name is hardcoded throughout .NET Business Service implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788124#action_12788124 ] Ben Dewey edited comment on STONEHENGE-110 at 12/9/09 3:37 PM: --- Nick, I just committed the fix for this issue, but verify, and resolve this ticket if all looks well. was (Author: bdewey01): Nick, I just committed the fix for this issue, but verify, and close this ticket if all looks well. DAL assembly name is hardcoded throughout .NET Business Service implementation -- Key: STONEHENGE-110 URL: https://issues.apache.org/jira/browse/STONEHENGE-110 Project: Stonehenge Issue Type: Bug Components: DOTNET_BS Affects Versions: M2 Reporter: Nicholas A Hauenstein Original Estimate: 1h Remaining Estimate: 1h I was looking through the .NET implementation of the business service (in TradeService.cs), and found a few instances of code like the following: dalCustomer = Trade.DALFactory.Customer.Create(Trade.DALSQLServer); Instead of something like the following: dalCustomer = Trade.DALFactory.Customer.Create(SQLHelper.GetAssemblyNameFromDBName(bsConfig.DBName)); It appears that we are hardcoding the usage of the SQL Server DAL in a few places within the service implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STONEHENGE-110) DAL assembly name is hardcoded throughout .NET Business Service implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12788124#action_12788124 ] Ben Dewey commented on STONEHENGE-110: -- Nick, I just committed the fix for this issue, but verify, and close this ticket if all looks well. DAL assembly name is hardcoded throughout .NET Business Service implementation -- Key: STONEHENGE-110 URL: https://issues.apache.org/jira/browse/STONEHENGE-110 Project: Stonehenge Issue Type: Bug Components: DOTNET_BS Affects Versions: M2 Reporter: Nicholas A Hauenstein Original Estimate: 1h Remaining Estimate: 1h I was looking through the .NET implementation of the business service (in TradeService.cs), and found a few instances of code like the following: dalCustomer = Trade.DALFactory.Customer.Create(Trade.DALSQLServer); Instead of something like the following: dalCustomer = Trade.DALFactory.Customer.Create(SQLHelper.GetAssemblyNameFromDBName(bsConfig.DBName)); It appears that we are hardcoding the usage of the SQL Server DAL in a few places within the service implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Dead Link: PHP MSSQL Driver
Chintana, Running PHP Client and BS on the new php_sqlsrv driver with PHP 5.2 works fine. Unfortunately, I'm getting an error when placing an order with the PHP_OPS or PHP_OPSSEC PHP_OPS Error: Fatal error: Uncaught WS FAULT exception: [soapenv:soapenv:MustUnderstand] Header not understood thrown in D:\wamp\www\php_stocktrader\trader_client\request_processor.php on line 923 PHP_OPSSEC Error: Fatal error: Uncaught WS FAULT exception: [soapenv:soapenv:Client] NULL parameter was passed when a non NULL parameter was expected thrown in D:\wamp\www\php_stocktrader\trader_client\request_processor.php on line 923 -Ben Dewey -Original Message- From: Chintana Wilamuna [mailto:chinta...@gmail.com] Sent: Tuesday, December 08, 2009 4:49 AM To: stonehenge-dev@incubator.apache.org Subject: Re: Dead Link: PHP MSSQL Driver On Tue, Dec 8, 2009 at 4:25 AM, Ben Dewey ben.de...@26ny.com wrote: The PHP MSSQL Driver is a dead link on the PHP documentation. Do you or Chintana have an updated link for this? Ben, The extension we were using has been discontinued from PHP 5.3. I just updated PHP stuff to use the latest MSSQL driver from Microsoft. Could you please take an svn up and try? The new driver location is - http://www.microsoft.com/downloads/details.aspx?displaylang=enFamilyID=ccdf728b-1ea0-48a8-a84a-5052214caad9 Bye, -Chintana -- http://engwar.com/
RE: StockTrader Sample Documentation Updates
Nick, This is great work. Very extensive. I am also not an expert on the Identity side so I didn't create those documents. I do have a couple comments though. 1. On the Sample App page you say The StockTrader Client and the [Passive STS] are managed by the online bank. I was under the impression that the client app would be managed by the brokerage firm and only the Passive STS would be managed by the online bank. This is also present in #4 of the walkthrough. 2. On the Sample App page I think we should add a Step 14/15 for the OPS updating the order record to closed and the Client app checking every page cycle for any newly closed orders and displaying them in the alert. -Ben Dewey From: Nick Hauenstein [ni...@quicklearn.com] Sent: Tuesday, December 08, 2009 7:24 PM To: stonehenge-dev@incubator.apache.org Subject: StockTrader Sample Documentation Updates Hello All, I took a stab at beginning documentation work for the StockTrader sample application. I am not a great scholar of claims-based security so if anyone would like to review and possibly edit/delete what is there, go right ahead. The main pages I touched were the following (and their respective children): http://cwiki.apache.org/confluence/display/STONEHENGE/Stonehenge+StockTrader+Sample+Application http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Client http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Business+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Configuration+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Order+Processor+Service http://cwiki.apache.org/confluence/display/STONEHENGE/StockTrader+Database If either of the main diagrams will require update, let me know and I can tweak them. Also, I'm holding off on creating the pages for the Active STS and Passive STS until everything is in working order and the precise requirements for each are known and well defined. - Nick
[jira] Commented: (STONEHENGE-109) WIF RC Support for .NET Implementation
[ https://issues.apache.org/jira/browse/STONEHENGE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12787489#action_12787489 ] Ben Dewey commented on STONEHENGE-109: -- Pablo, I've committed this code, please verify that the commit was successful, and resolve this ticket. WIF RC Support for .NET Implementation -- Key: STONEHENGE-109 URL: https://issues.apache.org/jira/browse/STONEHENGE-109 Project: Stonehenge Issue Type: Improvement Affects Versions: M2 Environment: .NET Reporter: Pablo Mariano Cibraro Attachments: wif_rc.patch I migrated all the existing code to use WIF RC. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Hardcoded DAL Bug?
Is there a Jira ticket created? Can someone create one? -Ben Dewey -Original Message- From: Pablo Cibraro [mailto:pablo.cibr...@tellago.com] Sent: Monday, December 07, 2009 2:31 PM To: stonehenge-dev@incubator.apache.org Subject: RE: Hardcoded DAL Bug? Hi Nick, Yes, it's something I mentioned in the past. That's code is wrong and it needs to be fixed to support MySql as well. Thanks Pablo. -Original Message- From: Nick Hauenstein [mailto:ni...@quicklearn.com] Sent: Monday, December 07, 2009 4:14 PM To: stonehenge-dev@incubator.apache.org Subject: Hardcoded DAL Bug? Hello, I was looking through the .NET implementation of the business service (in TradeService.cs), and found a few instances of code like the following: dalCustomer = Trade.DALFactory.Customer.Create(Trade.DALSQLServer); Instead of something like the following: dalCustomer = Trade.DALFactory.Customer.Create(SQLHelper.GetAssemblyNameFromDBName(bsConfig.DBName)); It appears that we are hardcoding the usage of the SQL Server DAL in a few places within the service implementation. Is that a bug, or is there a purpose behind this? - Nick
