SingleSignOn 1.1.0

Rating: No reviews yet
Downloads: 1080
Released: Sep 10, 2007
Updated: Sep 16, 2007 by nlb6665
Dev status: -not yet defined by owner-

Recommended Download

Source Code SingleSignOn_Source
source code, 962K, uploaded Sep 14, 2007 - 1080 downloads

Release Notes

This release completely replaces the old session security with a new key based security. I'm hoping it will be easier to manage and potentially more secure. It's open ended so anyone using this code is encouraged to create your own security models, use WCF, or change the management piece.

The default package includes a predefined key that you can use with the test programs as an example. I highly recommend changing that key if you use this outside a developer environment. I'll have more docs, instructions, etc to go along with this release as I complete them.

Feed back on this release is much appreciated. Please let me know in the discussions if you find anything buggy.

I'll have instructions for this release coming soon. I just wanted to get it out there so people could check it out.

Thanks,
-Nathan

Update
Okay, I messed up deploying this. I just replaced it with a new solution file so you don't get prompted to remove the source control bindings. If you still get it, just click, "Remove Bindings" or re-download this release. My apologies.

Instructions
Download and extract the release source. Open the solution file. Compile the code to make sure it builds. Select the Website project "SSOSite" and toggle its "Use dynamic ports" to false and set the port to 1388. Set your startup project to be either of the test client projects "SSOTestSite" or "TestWindowsClient." Then run the client. You should be able to login successfully with testuser or testadmin, both with password: testpass#

To run the admin tool, just set your startup project to be SSOSite and login to the admin site using testadmin. The admin site is a very quick and dirty solution to give you a little management site for your users. Feel free to make any necessary changes for your specific situation.

Security Setup
It's recommend that each application on each machine have its own security key file. So, to setup a new client, login to the admin site and go to the Service security screen. Create a new key file by clicking the Create Registration link at the top of the list. Enter an expiration date for the new key and click Save. This will refresh the list and show your new key. Click Download Key to download the key file and save it to your client application directory. You'll now need to setup your web service configuration to use the new key file by editing your app.config or web.config file. Create a new appsetting named "WebServiceKeyFile" with a value of the path to the key file. You can use "~/" for web applications or "@/" for paths relative to the executable. (I think this uses System.Windows.Forms.Application.ExecutablePath). Once you have the client setup with the key file, you can test it by logging in. (Also do not forget to setup your system.web.security settings to use the security provider model. Otherwise none of this will work. Take a look at the sample application config files to see more details.

Let me know if you have any questions. Just drop a line in the discussions.

Thanks

Reviews for this release

No reviews yet for this release.