identityserver / identityserver1 Goto Github PK

Hi,

I'm using IdentityServer v1 to passively authenticate two relying parties (both Silverlight apps, though I don't think that's relevant).

Upon signing out from one of the applications (using FederatedPassiveSignInStatus control), the application I signed out from redirects to the IdentityServer SignOut page, which displays two green ticks indicating that the cleaunp has succesfully taken place on both apps. So all ok so far.

The behaviour that I'm after is that upon signing out, the second RP should also redirect to the sign out page. Currently there is no redirection for the second RP, therefore giving the user the impression that they are still signed in (upon refreshing the browser for the 2nd RP, it redirects to the signin page, but I want this to happen upon signing out from the 1st RP).

Please can you provide me with some suggestions on how to get this to work? I tried including a wreply paramater in the signout request Url (in SignOut.cshtml) but this didn't resolve the issue.

Many Thanks,
James

When I open project with VS 2010 SP1, the website and test both project fails to open with below error:

The project type is not supported by this installation.

When I open code solution in VS 2012. The test project is not opening with same error.

can you fix this issue?

Hi,

I've deployed thinktecture v1 (copy of 3 months ago) to a server with the database on the same machine. I've developed some code against this older version and therefore want to keep using it. My problem is that I now want to move the identityserver to a separate machine from the aspnet database. This has created two problems:

1. If I copy the identity server folder from one machine to another and delete the configuration file in the App_Data the application states that the database has no signing certificate. It creates the database and I've checked that the application pool has read access to the private key of the ssl certificate, but it still does not work
2. How do I give the identity server access to the database using integrated security. both machines are on a domain but the IIS on the webserver is using a local user and this is not recognised by the sql server on the other machine.

Regards

Johan

I have set up IdentityServer1. But when I login, it throws me Bad key exception. I found below blog which have same issue but in Identity server 2.

IdentityServer/IdentityServer2#779

I have tried this solution but didn't work. Can you tell me what values should be added in -sky?

Hi, I've downloaded the source code and tried to run the application but I got value cannot be null exception.
It looks like the Thread.CurrentPrincipal is set to RolePrincipal so that it cannot be used as IClaimsPrincipal.
Why would that be?
When I first open the solution, there was a problem with the Microsoft.IdentityModel reference so I updated it on Nuget. Do you think that caused the problem?

Deniz

Do you intend to implement the optional wfresh parameter in the ws-federation protocol in the near future? We have a relying party that is able to set the required freshness, but IdentityServer is currently not doing anything with it. FYI, the relying party is a JAVA-application that uses the Fediz-component (http://cxf.apache.org/fediz.html) to support the ws-federation protocol and SAML-tokens. At the moment we are stuck with the IdentityServer default token lifetime, which is global for all relying parties and can only be set in hours.

I am using Thinktecture.IdentityModel.Web to implement basic authentication for a number of WCF services.

For various reasons, Ihave aspnetCompatibility set to true.
Most of the time, sending a request to the secured service with a valid Authorization header results in the Thread.CurrentPrincipal being set as expected. Occasionally, under load it seems to be set to the identity of a different user. This has resulted in user A managing to modify account information for user B.

After some research, I found a post that suggests the request may initiall start processing on one thread, but be completed on another and that this may cause us to lose the Thread.CurrentPrincipal.
http://piers7.blogspot.co.uk/2005/11/threadstatic-callcontext-and_02.html

Is this an issue that you have come across, and if so, can you suggest a workaround?

We need documentation...