You are viewing a plain text version of this content. The canonical link for it is here.
Posted to stonehenge-dev@incubator.apache.org by "Chintana Wilamuna (JIRA)" <ji...@apache.org> on 2009/11/26 12:03:39 UTC
[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-tabpanel&focusedCommentId=12782860#action_12782860 ]
Chintana Wilamuna commented on STONEHENGE-105:
----------------------------------------------
Pablo, token encryption in the active STS should be supported. Would it be possible for you to correct it and commit? Otherwise can't interoperate with the Identity Server.
> 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.
RE: [jira] Commented: (STONEHENGE-105) Remove SAML token encryption
from the .Net impl in order to interoperate with WSO2 Identity Server
Posted by Pablo Cibraro <Pa...@tellago.com>.
Yes, I will remove the token encryption from the passive STS. OpenSSO (for metro interop) is not supporting this either I think.
Thanks
Pablo.
-----Original Message-----
From: Chintana Wilamuna (JIRA) [mailto:jira@apache.org]
Sent: Thursday, November 26, 2009 9:04 AM
To: stonehenge-dev@incubator.apache.org
Subject: [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-tabpanel&focusedCommentId=12782860#action_12782860 ]
Chintana Wilamuna commented on STONEHENGE-105:
----------------------------------------------
Pablo, token encryption in the active STS should be supported. Would it be possible for you to correct it and commit? Otherwise can't interoperate with the Identity Server.
> 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.