Search Wiki:


SelfSTS is a simple utility which exposes a minimal WS-Federation STS endpoint. SelfSTS can be used as a test STS when developing web sites secured with Windows Identity Foundation.

The SelfSTS main UI. You can hide the SelfSTS UI and access it from the system tray when you need to change settings

SelfSTS has very limited system requirements. It does not require installation, and uses self-signed certificates from the file system rather than installing them in the stores. You can directly go in the bin\release folder and launch SelfSTS.exe from there. If you prefer to recompile. the solution file complete with source code is included.
You can easily edit the claim types and values that SelfSTS will issue:

The claim editing window

If you have the Windows SDK installed, you can use SelfSTS as a frontend for creating self-signed certificates. The Ui will automatically update the SelfSTS configuraiton to use the newly generated certificate for signing outgoing tokens. The certificates are generated directly on the file system, nothing gets persisted in the store.

The claim editing window

For more information, please see this blog post or the documentation included with the download package.

Last edited Sep 3 2010 at 6:22 AM  by Vittorio, version 3
dbrennan wrote  Jul 20 2011 at 1:40 PM  
I'm not an STS expert but I believe multiple claims of the same type are allowed. Unfortunately SelfSTS does not allow this as it is keyed on the ClaimType. It's a simple matter to change the key to DisplayName in ClaimsCollection.cs: GetElementKey() and ClaimConfigElement.cs: Constructor, Type and DisplayName properties. In my case this worked fine to add multiple role claims detectable with User.IsInRole() when debugging an Azure Application.

Page view tracker