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 <ch...@gmail.com> on 2009/10/13 14:00:35 UTC
.Net new passive STS impl.
Hi,
I'm trying out the new passive STS impl in .Net stocktrader in trunk.
When I try to access stocktrader home, it redirects me to the passive
STS. After logging in, I can see the message "you're logged in with
user id: uid:0".
Then there's two options for getting a new token or login with a
different user id. Trying to navigate to /trade/TradeHome.aspx result
in getting redirected to the same passive STS page. Shouldn't it
redirect to the /trade/TradeHome.aspx after getting a token?
Thanks in advance,
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
Yes, I think that would be a good idea.
Thanks
Pablo.
-----Original Message-----
From: Ben Dewey [mailto:Ben.Dewey@26ny.com]
Sent: Tuesday, October 13, 2009 12:57 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
Pablo,
I was just going to say that. Although keep in mind, if your asp.net application is running as NETWORK SERVICE (which it should be), then you'll have to choose the option to grant permission to \Everyone when running AuthorizeWcfServices.bat.
Also, Pablo, this step is currently optional in the readme. Should we change this to required?
-Ben Dewey
-----Original Message-----
From: Pablo Cibraro [mailto:Pablo.Cibraro@tellago.com]
Sent: Tuesday, October 13, 2009 11:53 AM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
Chintana,
The AuthorizeWcfServices.bat file in setup_utilities\Util gives the permissions that the ASP.NET account needs over the certificate. So, it just a matter of running that file to fix the issue.
Thanks
Pablo.
-----Original Message-----
From: Pablo Cibraro [mailto:Pablo.Cibraro@tellago.com]
Sent: Tuesday, October 13, 2009 12:25 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
The Passive STS is using the Trade.com (stocktraderpfxfile.pfx) certificate for encrypting and signing the SAML tokens. It is looking for that certificate in the Trusted People certificate store. Regarding the error you are getting, it could be caused by two things:
1. That certificate is not installed properly in the certificate store (Or the private key is missing)
2. The account running the ASP.NET process does not have rights to get access to the certificate private key.
If the STS can get access to that certificate, it will be able to issue a new token that you can use in the trade web application.
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Tuesday, October 13, 2009 12:14 PM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Tue, Oct 13, 2009 at 8:31 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> You should be redirected to the TradeHome.aspx page after getting a new token (selecting that option). I added that extra page in the passive STS to give the option of logging with another user (and getting a new token for that user). Not sure if the rest of the people is interested in having that functionality, if they are not, I can remove it.
Pablo,
When I login, I'm not getting redirected to TradeHome.aspx. It says on
the passive STS page.
After clicking the "click here to get a new token" button, I'm getting
an exception,
System.Security.Cryptography.CryptographicException: Keyset does not exist
Stack trace:
[CryptographicException: Keyset does not exist
]
System.Security.Cryptography.Utils.CreateProvHandle(CspParameters
parameters, Boolean randomKeyContainer) +369
System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType
keyType, CspParameters parameters, Boolean randomKeyContainer, Int32
dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle&
safeKeyHandle) +151
System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() +85
System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32
dwKeySize, CspParameters parameters, Boolean useDefaultKeySize) +280
System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()
+468
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.get_PrivateKey() +64
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.GetSignatureFormatter(String
algorithm) +22
Microsoft.IdentityModel.Protocols.XmlSignature.SignedXml.ComputeSignature(SecurityKey
signingKey) +522
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.ComputeSignature()
+187
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.OnEndRootElement()
+253
Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.WriteAssertion(XmlWriter
writer, SamlAssertion assertion) +839
Microsoft.IdentityModel.Tokens.EncryptedSecurityTokenHandler.WriteToken(XmlWriter
writer, SecurityToken token) +255
Microsoft.IdentityModel.Tokens.SecurityTokenSerializerAdapter.WriteTokenCore(XmlWriter
writer, SecurityToken token) +379
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteRSTRXml(XmlWriter
writer, String elementName, Object elementValue,
WSTrustSerializationContext context, WSTrustConstantsAdapter
trustConstants) +932
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +477
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context) +70
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteResponse(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +271
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteXml(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context) +121
Microsoft.IdentityModel.Protocols.WSFederation.WSFederationSerializer.GetResponseAsString(RequestSecurityTokenResponse
response, WSTrustSerializationContext context) +182
Microsoft.IdentityModel.Protocols.WSFederation.SignInResponseMessage..ctor(Uri
baseUrl, RequestSecurityTokenResponse response, WSFederationSerializer
federationSerializer, WSTrustSerializationContext context) +94
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.ProcessSignInRequest(SignInRequestMessage
requestMessage) +372
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.OnPreRender(EventArgs
e) +1621
System.Web.UI.Control.PreRenderRecursiveInternal() +108
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+3394
Any idea what I may be doing wrong? Or a step I might have missed?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Ben Dewey <Be...@26ny.com>.
Pablo,
I was just going to say that. Although keep in mind, if your asp.net application is running as NETWORK SERVICE (which it should be), then you'll have to choose the option to grant permission to \Everyone when running AuthorizeWcfServices.bat.
Also, Pablo, this step is currently optional in the readme. Should we change this to required?
-Ben Dewey
-----Original Message-----
From: Pablo Cibraro [mailto:Pablo.Cibraro@tellago.com]
Sent: Tuesday, October 13, 2009 11:53 AM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
Chintana,
The AuthorizeWcfServices.bat file in setup_utilities\Util gives the permissions that the ASP.NET account needs over the certificate. So, it just a matter of running that file to fix the issue.
Thanks
Pablo.
-----Original Message-----
From: Pablo Cibraro [mailto:Pablo.Cibraro@tellago.com]
Sent: Tuesday, October 13, 2009 12:25 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
The Passive STS is using the Trade.com (stocktraderpfxfile.pfx) certificate for encrypting and signing the SAML tokens. It is looking for that certificate in the Trusted People certificate store. Regarding the error you are getting, it could be caused by two things:
1. That certificate is not installed properly in the certificate store (Or the private key is missing)
2. The account running the ASP.NET process does not have rights to get access to the certificate private key.
If the STS can get access to that certificate, it will be able to issue a new token that you can use in the trade web application.
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Tuesday, October 13, 2009 12:14 PM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Tue, Oct 13, 2009 at 8:31 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> You should be redirected to the TradeHome.aspx page after getting a new token (selecting that option). I added that extra page in the passive STS to give the option of logging with another user (and getting a new token for that user). Not sure if the rest of the people is interested in having that functionality, if they are not, I can remove it.
Pablo,
When I login, I'm not getting redirected to TradeHome.aspx. It says on
the passive STS page.
After clicking the "click here to get a new token" button, I'm getting
an exception,
System.Security.Cryptography.CryptographicException: Keyset does not exist
Stack trace:
[CryptographicException: Keyset does not exist
]
System.Security.Cryptography.Utils.CreateProvHandle(CspParameters
parameters, Boolean randomKeyContainer) +369
System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType
keyType, CspParameters parameters, Boolean randomKeyContainer, Int32
dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle&
safeKeyHandle) +151
System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() +85
System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32
dwKeySize, CspParameters parameters, Boolean useDefaultKeySize) +280
System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()
+468
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.get_PrivateKey() +64
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.GetSignatureFormatter(String
algorithm) +22
Microsoft.IdentityModel.Protocols.XmlSignature.SignedXml.ComputeSignature(SecurityKey
signingKey) +522
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.ComputeSignature()
+187
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.OnEndRootElement()
+253
Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.WriteAssertion(XmlWriter
writer, SamlAssertion assertion) +839
Microsoft.IdentityModel.Tokens.EncryptedSecurityTokenHandler.WriteToken(XmlWriter
writer, SecurityToken token) +255
Microsoft.IdentityModel.Tokens.SecurityTokenSerializerAdapter.WriteTokenCore(XmlWriter
writer, SecurityToken token) +379
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteRSTRXml(XmlWriter
writer, String elementName, Object elementValue,
WSTrustSerializationContext context, WSTrustConstantsAdapter
trustConstants) +932
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +477
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context) +70
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteResponse(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +271
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteXml(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context) +121
Microsoft.IdentityModel.Protocols.WSFederation.WSFederationSerializer.GetResponseAsString(RequestSecurityTokenResponse
response, WSTrustSerializationContext context) +182
Microsoft.IdentityModel.Protocols.WSFederation.SignInResponseMessage..ctor(Uri
baseUrl, RequestSecurityTokenResponse response, WSFederationSerializer
federationSerializer, WSTrustSerializationContext context) +94
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.ProcessSignInRequest(SignInRequestMessage
requestMessage) +372
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.OnPreRender(EventArgs
e) +1621
System.Web.UI.Control.PreRenderRecursiveInternal() +108
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+3394
Any idea what I may be doing wrong? Or a step I might have missed?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
Chintana,
The AuthorizeWcfServices.bat file in setup_utilities\Util gives the permissions that the ASP.NET account needs over the certificate. So, it just a matter of running that file to fix the issue.
Thanks
Pablo.
-----Original Message-----
From: Pablo Cibraro [mailto:Pablo.Cibraro@tellago.com]
Sent: Tuesday, October 13, 2009 12:25 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
The Passive STS is using the Trade.com (stocktraderpfxfile.pfx) certificate for encrypting and signing the SAML tokens. It is looking for that certificate in the Trusted People certificate store. Regarding the error you are getting, it could be caused by two things:
1. That certificate is not installed properly in the certificate store (Or the private key is missing)
2. The account running the ASP.NET process does not have rights to get access to the certificate private key.
If the STS can get access to that certificate, it will be able to issue a new token that you can use in the trade web application.
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Tuesday, October 13, 2009 12:14 PM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Tue, Oct 13, 2009 at 8:31 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> You should be redirected to the TradeHome.aspx page after getting a new token (selecting that option). I added that extra page in the passive STS to give the option of logging with another user (and getting a new token for that user). Not sure if the rest of the people is interested in having that functionality, if they are not, I can remove it.
Pablo,
When I login, I'm not getting redirected to TradeHome.aspx. It says on
the passive STS page.
After clicking the "click here to get a new token" button, I'm getting
an exception,
System.Security.Cryptography.CryptographicException: Keyset does not exist
Stack trace:
[CryptographicException: Keyset does not exist
]
System.Security.Cryptography.Utils.CreateProvHandle(CspParameters
parameters, Boolean randomKeyContainer) +369
System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType
keyType, CspParameters parameters, Boolean randomKeyContainer, Int32
dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle&
safeKeyHandle) +151
System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() +85
System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32
dwKeySize, CspParameters parameters, Boolean useDefaultKeySize) +280
System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()
+468
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.get_PrivateKey() +64
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.GetSignatureFormatter(String
algorithm) +22
Microsoft.IdentityModel.Protocols.XmlSignature.SignedXml.ComputeSignature(SecurityKey
signingKey) +522
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.ComputeSignature()
+187
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.OnEndRootElement()
+253
Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.WriteAssertion(XmlWriter
writer, SamlAssertion assertion) +839
Microsoft.IdentityModel.Tokens.EncryptedSecurityTokenHandler.WriteToken(XmlWriter
writer, SecurityToken token) +255
Microsoft.IdentityModel.Tokens.SecurityTokenSerializerAdapter.WriteTokenCore(XmlWriter
writer, SecurityToken token) +379
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteRSTRXml(XmlWriter
writer, String elementName, Object elementValue,
WSTrustSerializationContext context, WSTrustConstantsAdapter
trustConstants) +932
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +477
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context) +70
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteResponse(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +271
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteXml(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context) +121
Microsoft.IdentityModel.Protocols.WSFederation.WSFederationSerializer.GetResponseAsString(RequestSecurityTokenResponse
response, WSTrustSerializationContext context) +182
Microsoft.IdentityModel.Protocols.WSFederation.SignInResponseMessage..ctor(Uri
baseUrl, RequestSecurityTokenResponse response, WSFederationSerializer
federationSerializer, WSTrustSerializationContext context) +94
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.ProcessSignInRequest(SignInRequestMessage
requestMessage) +372
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.OnPreRender(EventArgs
e) +1621
System.Web.UI.Control.PreRenderRecursiveInternal() +108
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+3394
Any idea what I may be doing wrong? Or a step I might have missed?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Ben Dewey <Be...@26ny.com>.
We've discussed this numerous times in the past and I have to agree with Kent that, although ideal, it's very unlikely that we'll have a single customBinding configuration that will work with all cases.
This is why the SERVICE names from the DB maps directly to a App.config setting [1] that in turn binds to a client endpoint[2]. Please note, although present, the address property of the client endpoint is not actually used and is replaced by the address of the SERVICE from the DB.
That being said, there are improvements that can be made. First, I'm not sure what value the .NET wsHttp endpoint adds. It's currently only being used by .NET and IMHO, only adds unnecessary confusion. Second, the basic and all non-.NET OPSSEC clients are using the same configs; this could be consolidated to something like [3].
-Ben Dewey
[1]
<add key="DOTNET_OPS" value="OpsClient_DotNet_BasicHttpBinding" />
<add key="DOTNET_OPSSEC" value="OpsClient_DotNet_WsHttpBinding_MSec" />
<add key="PHP_OPS" value="OpsClient_PHP_BasicHttpBinding" />
<add key="PHP_OPSSEC" value="OpsClient_PHP_WsHttpBinding_MSec" />
<add key="JAVA_OPS" value="OpsClient_WSAS_BasicHttpBinding" />
<add key="JAVA_OPSSEC" value="OpsClient_WSAS_WsHttpBinding_MSec" />
[2]
<endpoint address="http://localhost:8000/tradeorderprocessor/msec"
contract="Trade.OrderProcessorContract.IOrderProcessor"
binding="wsHttpBinding" bindingConfiguration="OpsClient_WsHttpBinding_MSec"
behaviorConfiguration="OpsClient_DotNet_CertificateBehavior"
name="OpsClient_DotNet_WsHttpBinding_MSec">
<identity>
<dns value="OPS.Com"/>
</identity>
</endpoint>
[3]
<add key="DOTNET_OPS" value="OpsClient_BasicHttpBinding" />
<add key="DOTNET_OPSSEC" value="OpsClient_DotNet_WsHttpBinding_MSec" />
<add key="PHP_OPS" value="OpsClient_BasicHttpBinding" />
<add key="PHP_OPSSEC" value="OpsClient_CustomBinding_MSec" />
<add key="JAVA_OPS" value="OpsClient_BasicHttpBinding" />
<add key="JAVA_OPSSEC" value="OpsClient_CustomBinding_MSec" />
-----Original Message-----
From: Kent Brown [mailto:Kent.Brown@microsoft.com]
Sent: Friday, October 16, 2009 10:29 AM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
I agree that's the way it "should" work if interop was perfect. My only concern is whether we will hit situations where special bindings are needed on one side or the other to get things to work.
I think that would be a big change in the way the config service works and the way the .NET app uses it. Maybe Ben or others can weigh in on the implications before we change it.
Kent
-----Original Message-----
From: Pablo Cibraro [mailto:Pablo.Cibraro@tellago.com]
Sent: Friday, October 16, 2009 4:57 AM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
Yes, I totally agree that it should work that way. I'll be working on this today.
Thanks
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Friday, October 16, 2009 6:50 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Wed, Oct 14, 2009 at 9:49 PM, Pablo Cibraro <Pa...@tellago.com> wrote:
> Ok, I will take a look. I had some problems to build the WSAS implementation the last time I tried some weeks ago, so I never tested our .NET implementation with other implementations.
Keeping the setup as DOTNET_CLIENT -> DOTNET_BS and by changing the DOTNET_BS endpoint in the database to point it to the WSAS_BS and changing the endpoint value in web.config sends the request to the WSAS_BS. So, it seems to be trader client in .Net is checking whether the business service is .Net, WSAS etc... and then invoking it. I think it's best if we can remove this tight coupling. Ideal scenario would be you get the endpoint from the database, you know that's where the business service resides and just call that service.
Thoughts?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Kent Brown <Ke...@microsoft.com>.
I agree that's the way it "should" work if interop was perfect. My only concern is whether we will hit situations where special bindings are needed on one side or the other to get things to work.
I think that would be a big change in the way the config service works and the way the .NET app uses it. Maybe Ben or others can weigh in on the implications before we change it.
Kent
-----Original Message-----
From: Pablo Cibraro [mailto:Pablo.Cibraro@tellago.com]
Sent: Friday, October 16, 2009 4:57 AM
To: stonehenge-dev@incubator.apache.org
Subject: RE: .Net new passive STS impl.
Yes, I totally agree that it should work that way. I'll be working on this today.
Thanks
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Friday, October 16, 2009 6:50 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Wed, Oct 14, 2009 at 9:49 PM, Pablo Cibraro <Pa...@tellago.com> wrote:
> Ok, I will take a look. I had some problems to build the WSAS implementation the last time I tried some weeks ago, so I never tested our .NET implementation with other implementations.
Keeping the setup as DOTNET_CLIENT -> DOTNET_BS and by changing the DOTNET_BS endpoint in the database to point it to the WSAS_BS and changing the endpoint value in web.config sends the request to the WSAS_BS. So, it seems to be trader client in .Net is checking whether the business service is .Net, WSAS etc... and then invoking it. I think it's best if we can remove this tight coupling. Ideal scenario would be you get the endpoint from the database, you know that's where the business service resides and just call that service.
Thoughts?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
Yes, I totally agree that it should work that way. I'll be working on this today.
Thanks
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Friday, October 16, 2009 6:50 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Wed, Oct 14, 2009 at 9:49 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> Ok, I will take a look. I had some problems to build the WSAS implementation the last time I tried some weeks ago, so I never tested our .NET implementation with other implementations.
Keeping the setup as DOTNET_CLIENT -> DOTNET_BS and by changing the
DOTNET_BS endpoint in the database to point it to the WSAS_BS and
changing the endpoint value in web.config sends the request to the
WSAS_BS. So, it seems to be trader client in .Net is checking whether
the business service is .Net, WSAS etc... and then invoking it. I
think it's best if we can remove this tight coupling. Ideal scenario
would be you get the endpoint from the database, you know that's where
the business service resides and just call that service.
Thoughts?
Bye,
-Chintana
--
http://engwar.com/
Re: .Net new passive STS impl.
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Wed, Oct 14, 2009 at 9:49 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> Ok, I will take a look. I had some problems to build the WSAS implementation the last time I tried some weeks ago, so I never tested our .NET implementation with other implementations.
Keeping the setup as DOTNET_CLIENT -> DOTNET_BS and by changing the
DOTNET_BS endpoint in the database to point it to the WSAS_BS and
changing the endpoint value in web.config sends the request to the
WSAS_BS. So, it seems to be trader client in .Net is checking whether
the business service is .Net, WSAS etc... and then invoking it. I
think it's best if we can remove this tight coupling. Ideal scenario
would be you get the endpoint from the database, you know that's where
the business service resides and just call that service.
Thoughts?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
Ok, I will take a look. I had some problems to build the WSAS implementation the last time I tried some weeks ago, so I never tested our .NET implementation with other implementations.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Wednesday, October 14, 2009 10:53 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Wed, Oct 14, 2009 at 7:02 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> Yes, that's correct. The DOTNET_BS call the service using the token it got from the Active STS. The service not only validates the token, but also it gets the User profile id from the token claims (or assertions). The rest of the business logic wasn't changed.
>
> Is the WSAS_BS endpoint expecting a SAML token ?.
Not at the moment, I'm trying to get it accept the request coming from
the .Net client so that I can validate the token. But the request
never comes to the service. It gives the exception before actually
invoking the service.
Bye,
-Chintana
--
http://engwar.com/
Re: .Net new passive STS impl.
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Wed, Oct 14, 2009 at 7:02 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> Yes, that's correct. The DOTNET_BS call the service using the token it got from the Active STS. The service not only validates the token, but also it gets the User profile id from the token claims (or assertions). The rest of the business logic wasn't changed.
>
> Is the WSAS_BS endpoint expecting a SAML token ?.
Not at the moment, I'm trying to get it accept the request coming from
the .Net client so that I can validate the token. But the request
never comes to the service. It gives the exception before actually
invoking the service.
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
Yes, that's correct. The DOTNET_BS call the service using the token it got from the Active STS. The service not only validates the token, but also it gets the User profile id from the token claims (or assertions). The rest of the business logic wasn't changed.
Is the WSAS_BS endpoint expecting a SAML token ?.
Thanks
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Wednesday, October 14, 2009 10:09 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Wed, Oct 14, 2009 at 6:26 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> There is a problem there, the DOTNET_BS endpoint has been changed to support claim based security (it expects a SAML token with the user claims). Therefore, the DOTNET_CLIENT client is negotiating a SAML token before calling that service. I don't think the WSAS_BS endpoint is expecting that.
Pablo,
Isn't it suppose to be, you call the service giving the SAML token you
got from the STS so the service will try to validate the token and
then goes into the normal business logic?
Bye,
-Chintana
--
http://engwar.com/
Re: .Net new passive STS impl.
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Wed, Oct 14, 2009 at 6:26 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> There is a problem there, the DOTNET_BS endpoint has been changed to support claim based security (it expects a SAML token with the user claims). Therefore, the DOTNET_CLIENT client is negotiating a SAML token before calling that service. I don't think the WSAS_BS endpoint is expecting that.
Pablo,
Isn't it suppose to be, you call the service giving the SAML token you
got from the STS so the service will try to validate the token and
then goes into the normal business logic?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
There is a problem there, the DOTNET_BS endpoint has been changed to support claim based security (it expects a SAML token with the user claims). Therefore, the DOTNET_CLIENT client is negotiating a SAML token before calling that service. I don't think the WSAS_BS endpoint is expecting that.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Wednesday, October 14, 2009 6:19 AM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Tue, Oct 13, 2009 at 11:06 PM, Chintana Wilamuna <ch...@gmail.com> wrote:
> On Tue, Oct 13, 2009 at 10:50 PM, Pablo Cibraro
> <Pa...@tellago.com> wrote:
>
>> "System.Reflection.AmbiguousMatchException: Ambiguous match found. ". It looks like an issue with the binaries, could you please, cleanup all the binary folders and rebuild everything from scratch ?. If the problem still exists after that, let me know.
>
> I tried with BuildDotNet.cmd and also tried opening up each .sln,
> build everything after cleaning. In both instances, I'm seeing the
> same exception.
This situation only occurs when the setup is DOTNET_CLIENT -> WSAS_BS.
For DOTNET_CLIENT -> DOTNET_BS it doesn't give this error and
everything work as expected.
Wonder whether I have to do any extra step after changing to the WSAS_BS.
Bye,
-Chintana
--
http://engwar.com/
Re: .Net new passive STS impl.
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Tue, Oct 13, 2009 at 11:06 PM, Chintana Wilamuna <ch...@gmail.com> wrote:
> On Tue, Oct 13, 2009 at 10:50 PM, Pablo Cibraro
> <Pa...@tellago.com> wrote:
>
>> "System.Reflection.AmbiguousMatchException: Ambiguous match found. ". It looks like an issue with the binaries, could you please, cleanup all the binary folders and rebuild everything from scratch ?. If the problem still exists after that, let me know.
>
> I tried with BuildDotNet.cmd and also tried opening up each .sln,
> build everything after cleaning. In both instances, I'm seeing the
> same exception.
This situation only occurs when the setup is DOTNET_CLIENT -> WSAS_BS.
For DOTNET_CLIENT -> DOTNET_BS it doesn't give this error and
everything work as expected.
Wonder whether I have to do any extra step after changing to the WSAS_BS.
Bye,
-Chintana
--
http://engwar.com/
Re: .Net new passive STS impl.
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Tue, Oct 13, 2009 at 10:50 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> "System.Reflection.AmbiguousMatchException: Ambiguous match found. ". It looks like an issue with the binaries, could you please, cleanup all the binary folders and rebuild everything from scratch ?. If the problem still exists after that, let me know.
I tried with BuildDotNet.cmd and also tried opening up each .sln,
build everything after cleaning. In both instances, I'm seeing the
same exception.
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
"System.Reflection.AmbiguousMatchException: Ambiguous match found. ". It looks like an issue with the binaries, could you please, cleanup all the binary folders and rebuild everything from scratch ?. If the problem still exists after that, let me know.
Thanks
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Tuesday, October 13, 2009 2:08 PM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Tue, Oct 13, 2009 at 8:54 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> The Passive STS is using the Trade.com (stocktraderpfxfile.pfx) certificate for encrypting and signing the SAML tokens. It is looking for that certificate in the Trusted People certificate store. Regarding the error you are getting, it could be caused by two things:
>
> 1. That certificate is not installed properly in the certificate store (Or the private key is missing)
> 2. The account running the ASP.NET process does not have rights to get access to the certificate private key.
>
> If the STS can get access to that certificate, it will be able to issue a new token that you can use in the trade web application.
Understood.
Ran AuthorizeWcfServices.bat and set reservation for current user as
well as \Everyone. Now I'm getting the following exception,
System.Reflection.AmbiguousMatchException: Ambiguous match found.
Stack Trace:
[AmbiguousMatchException: Ambiguous match found.]
System.DefaultBinder.BindToMethod(BindingFlags bindingAttr,
MethodBase[] canidates, Object[]& args, ParameterModifier[] modifiers,
CultureInfo cultureInfo, String[] names, Object& state) +10242693
System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes) +10364331
System.Activator.CreateInstance(Type type, Object[] args) +38
Trade.Client.Connection`1.createChannelFactory(String
clientConfiguration, String url, String userName, String password,
Boolean useClaims) in
D:\src\stonehenge-trunk\stocktrader\dotnet\common\BasicClient\BasicClient.cs:93
Trade.Client.Connection`1.get_Channel() in
D:\src\stonehenge-trunk\stocktrader\dotnet\common\BasicClient\BasicClient.cs:202
Trade.Client.Client`1.get_Channel() in
D:\src\stonehenge-trunk\stocktrader\dotnet\common\BasicClient\BasicClient.cs:317
Trade.BusinessServiceClient.BusinessServiceClient.get_Channel() in
D:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\BusinessServiceClient\BusinessServiceClient.cs:107
Trade.BusinessServiceClient.BusinessServiceClient.getAccountData(String
userID) in D:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\BusinessServiceClient\BusinessServiceClient.cs:178
Trade.BusinessServiceClient.BSLClient.getAccountData(String userID)
in D:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\BusinessServiceClient\BSLClient.cs:173
Trade.Web.TradeHome.Page_Load(Object sender, EventArgs e) in
d:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\Trade\TradeHome.aspx.cs:56
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp,
Object o, Object t, EventArgs e) +25
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object
sender, EventArgs e) +42
System.Web.UI.Control.OnLoad(EventArgs e) +132
System.Web.UI.Control.LoadRecursive() +66
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+2428
Any pointers would be highly appreciated.
Bye,
-Chintana
--
http://engwar.com/
Re: .Net new passive STS impl.
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Tue, Oct 13, 2009 at 8:54 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> The Passive STS is using the Trade.com (stocktraderpfxfile.pfx) certificate for encrypting and signing the SAML tokens. It is looking for that certificate in the Trusted People certificate store. Regarding the error you are getting, it could be caused by two things:
>
> 1. That certificate is not installed properly in the certificate store (Or the private key is missing)
> 2. The account running the ASP.NET process does not have rights to get access to the certificate private key.
>
> If the STS can get access to that certificate, it will be able to issue a new token that you can use in the trade web application.
Understood.
Ran AuthorizeWcfServices.bat and set reservation for current user as
well as \Everyone. Now I'm getting the following exception,
System.Reflection.AmbiguousMatchException: Ambiguous match found.
Stack Trace:
[AmbiguousMatchException: Ambiguous match found.]
System.DefaultBinder.BindToMethod(BindingFlags bindingAttr,
MethodBase[] canidates, Object[]& args, ParameterModifier[] modifiers,
CultureInfo cultureInfo, String[] names, Object& state) +10242693
System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes) +10364331
System.Activator.CreateInstance(Type type, Object[] args) +38
Trade.Client.Connection`1.createChannelFactory(String
clientConfiguration, String url, String userName, String password,
Boolean useClaims) in
D:\src\stonehenge-trunk\stocktrader\dotnet\common\BasicClient\BasicClient.cs:93
Trade.Client.Connection`1.get_Channel() in
D:\src\stonehenge-trunk\stocktrader\dotnet\common\BasicClient\BasicClient.cs:202
Trade.Client.Client`1.get_Channel() in
D:\src\stonehenge-trunk\stocktrader\dotnet\common\BasicClient\BasicClient.cs:317
Trade.BusinessServiceClient.BusinessServiceClient.get_Channel() in
D:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\BusinessServiceClient\BusinessServiceClient.cs:107
Trade.BusinessServiceClient.BusinessServiceClient.getAccountData(String
userID) in D:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\BusinessServiceClient\BusinessServiceClient.cs:178
Trade.BusinessServiceClient.BSLClient.getAccountData(String userID)
in D:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\BusinessServiceClient\BSLClient.cs:173
Trade.Web.TradeHome.Page_Load(Object sender, EventArgs e) in
d:\src\stonehenge-trunk\stocktrader\dotnet\trader_client\Trade\TradeHome.aspx.cs:56
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp,
Object o, Object t, EventArgs e) +25
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object
sender, EventArgs e) +42
System.Web.UI.Control.OnLoad(EventArgs e) +132
System.Web.UI.Control.LoadRecursive() +66
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+2428
Any pointers would be highly appreciated.
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
The Passive STS is using the Trade.com (stocktraderpfxfile.pfx) certificate for encrypting and signing the SAML tokens. It is looking for that certificate in the Trusted People certificate store. Regarding the error you are getting, it could be caused by two things:
1. That certificate is not installed properly in the certificate store (Or the private key is missing)
2. The account running the ASP.NET process does not have rights to get access to the certificate private key.
If the STS can get access to that certificate, it will be able to issue a new token that you can use in the trade web application.
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Tuesday, October 13, 2009 12:14 PM
To: stonehenge-dev@incubator.apache.org
Subject: Re: .Net new passive STS impl.
On Tue, Oct 13, 2009 at 8:31 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> You should be redirected to the TradeHome.aspx page after getting a new token (selecting that option). I added that extra page in the passive STS to give the option of logging with another user (and getting a new token for that user). Not sure if the rest of the people is interested in having that functionality, if they are not, I can remove it.
Pablo,
When I login, I'm not getting redirected to TradeHome.aspx. It says on
the passive STS page.
After clicking the "click here to get a new token" button, I'm getting
an exception,
System.Security.Cryptography.CryptographicException: Keyset does not exist
Stack trace:
[CryptographicException: Keyset does not exist
]
System.Security.Cryptography.Utils.CreateProvHandle(CspParameters
parameters, Boolean randomKeyContainer) +369
System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType
keyType, CspParameters parameters, Boolean randomKeyContainer, Int32
dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle&
safeKeyHandle) +151
System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() +85
System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32
dwKeySize, CspParameters parameters, Boolean useDefaultKeySize) +280
System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()
+468
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.get_PrivateKey() +64
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.GetSignatureFormatter(String
algorithm) +22
Microsoft.IdentityModel.Protocols.XmlSignature.SignedXml.ComputeSignature(SecurityKey
signingKey) +522
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.ComputeSignature()
+187
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.OnEndRootElement()
+253
Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.WriteAssertion(XmlWriter
writer, SamlAssertion assertion) +839
Microsoft.IdentityModel.Tokens.EncryptedSecurityTokenHandler.WriteToken(XmlWriter
writer, SecurityToken token) +255
Microsoft.IdentityModel.Tokens.SecurityTokenSerializerAdapter.WriteTokenCore(XmlWriter
writer, SecurityToken token) +379
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteRSTRXml(XmlWriter
writer, String elementName, Object elementValue,
WSTrustSerializationContext context, WSTrustConstantsAdapter
trustConstants) +932
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +477
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context) +70
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteResponse(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +271
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteXml(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context) +121
Microsoft.IdentityModel.Protocols.WSFederation.WSFederationSerializer.GetResponseAsString(RequestSecurityTokenResponse
response, WSTrustSerializationContext context) +182
Microsoft.IdentityModel.Protocols.WSFederation.SignInResponseMessage..ctor(Uri
baseUrl, RequestSecurityTokenResponse response, WSFederationSerializer
federationSerializer, WSTrustSerializationContext context) +94
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.ProcessSignInRequest(SignInRequestMessage
requestMessage) +372
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.OnPreRender(EventArgs
e) +1621
System.Web.UI.Control.PreRenderRecursiveInternal() +108
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+3394
Any idea what I may be doing wrong? Or a step I might have missed?
Bye,
-Chintana
--
http://engwar.com/
Re: .Net new passive STS impl.
Posted by Chintana Wilamuna <ch...@gmail.com>.
On Tue, Oct 13, 2009 at 8:31 PM, Pablo Cibraro
<Pa...@tellago.com> wrote:
> You should be redirected to the TradeHome.aspx page after getting a new token (selecting that option). I added that extra page in the passive STS to give the option of logging with another user (and getting a new token for that user). Not sure if the rest of the people is interested in having that functionality, if they are not, I can remove it.
Pablo,
When I login, I'm not getting redirected to TradeHome.aspx. It says on
the passive STS page.
After clicking the "click here to get a new token" button, I'm getting
an exception,
System.Security.Cryptography.CryptographicException: Keyset does not exist
Stack trace:
[CryptographicException: Keyset does not exist
]
System.Security.Cryptography.Utils.CreateProvHandle(CspParameters
parameters, Boolean randomKeyContainer) +369
System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType
keyType, CspParameters parameters, Boolean randomKeyContainer, Int32
dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle&
safeKeyHandle) +151
System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() +85
System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32
dwKeySize, CspParameters parameters, Boolean useDefaultKeySize) +280
System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()
+468
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.get_PrivateKey() +64
System.IdentityModel.Tokens.X509AsymmetricSecurityKey.GetSignatureFormatter(String
algorithm) +22
Microsoft.IdentityModel.Protocols.XmlSignature.SignedXml.ComputeSignature(SecurityKey
signingKey) +522
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.ComputeSignature()
+187
Microsoft.IdentityModel.Protocols.XmlSignature.EnvelopedSignatureWriter.OnEndRootElement()
+253
Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.WriteAssertion(XmlWriter
writer, SamlAssertion assertion) +839
Microsoft.IdentityModel.Tokens.EncryptedSecurityTokenHandler.WriteToken(XmlWriter
writer, SecurityToken token) +255
Microsoft.IdentityModel.Tokens.SecurityTokenSerializerAdapter.WriteTokenCore(XmlWriter
writer, SecurityToken token) +379
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteRSTRXml(XmlWriter
writer, String elementName, Object elementValue,
WSTrustSerializationContext context, WSTrustConstantsAdapter
trustConstants) +932
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +477
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteKnownResponseElement(RequestSecurityTokenResponse
rstr, XmlWriter writer, WSTrustSerializationContext context) +70
Microsoft.IdentityModel.Protocols.WSTrust.WSTrustSerializationHelper.WriteResponse(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context,
WSTrustResponseSerializer responseSerializer, WSTrustConstantsAdapter
trustConstants) +271
Microsoft.IdentityModel.Protocols.WSTrust.WSTrust13ResponseSerializer.WriteXml(RequestSecurityTokenResponse
response, XmlWriter writer, WSTrustSerializationContext context) +121
Microsoft.IdentityModel.Protocols.WSFederation.WSFederationSerializer.GetResponseAsString(RequestSecurityTokenResponse
response, WSTrustSerializationContext context) +182
Microsoft.IdentityModel.Protocols.WSFederation.SignInResponseMessage..ctor(Uri
baseUrl, RequestSecurityTokenResponse response, WSFederationSerializer
federationSerializer, WSTrustSerializationContext context) +94
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.ProcessSignInRequest(SignInRequestMessage
requestMessage) +372
Microsoft.IdentityModel.Web.Controls.FederatedPassiveTokenService.OnPreRender(EventArgs
e) +1621
System.Web.UI.Control.PreRenderRecursiveInternal() +108
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+3394
Any idea what I may be doing wrong? Or a step I might have missed?
Bye,
-Chintana
--
http://engwar.com/
RE: .Net new passive STS impl.
Posted by Pablo Cibraro <Pa...@tellago.com>.
Hi Chintana,
You should be redirected to the TradeHome.aspx page after getting a new token (selecting that option). I added that extra page in the passive STS to give the option of logging with another user (and getting a new token for that user). Not sure if the rest of the people is interested in having that functionality, if they are not, I can remove it.
Thanks
Pablo.
-----Original Message-----
From: Chintana Wilamuna [mailto:chintanaw@gmail.com]
Sent: Tuesday, October 13, 2009 11:01 AM
To: stonehenge-dev@incubator.apache.org
Subject: .Net new passive STS impl.
Hi,
I'm trying out the new passive STS impl in .Net stocktrader in trunk.
When I try to access stocktrader home, it redirects me to the passive
STS. After logging in, I can see the message "you're logged in with
user id: uid:0".
Then there's two options for getting a new token or login with a
different user id. Trying to navigate to /trade/TradeHome.aspx result
in getting redirected to the same passive STS page. Shouldn't it
redirect to the /trade/TradeHome.aspx after getting a token?
Thanks in advance,
Bye,
-Chintana
--
http://engwar.com/