Ben, Yes, sure. I will test this today.
Thanks Pablo. -----Original Message----- From: Ben Dewey [mailto:ben.de...@26ny.com] Sent: Monday, October 26, 2009 10:50 AM To: stonehenge-dev@incubator.apache.org Subject: RE: [jira] Updated: (STONEHENGE-105) Remove SAML token encryption from the .Net impl in order to interoperate with WSO2 Identity Server Chintana, I'm assuming that you are providing this as a patch so the .NET team can test before committing. If there is another reason place clarify. Pablo, Can you please test these patches against the .NET trunk so Chintana can commit this. -Ben Dewey -----Original Message----- From: Chintana Wilamuna (JIRA) [mailto:j...@apache.org] Sent: Saturday, October 24, 2009 2:25 AM To: stonehenge-dev@incubator.apache.org Subject: [jira] Updated: (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:all-tabpanel ] Chintana Wilamuna updated STONEHENGE-105: ----------------------------------------- Attachment: trader-client-web-config.patch Changing the trader client to work with an unencrypted token. trader-client-web-config.patch: * Removing audience restrictions as Identity Server cannot do audienceRestritions * Adding the passive STS reference pointing to the Identity Server (commented out by default) * Adding the Identity Server public cert > 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. - You can reply to this email to add a comment to the issue online.
