SingleSignOn 2.0 Beta

Rating:        Based on 1 rating
Reviewed:  1 review
Downloads: 5065
Released: Mar 28, 2008
Updated: Mar 31, 2008 by nlb6665
Dev status: -not yet defined by owner-

Recommended Download

Source Code SingleSignOn_Source_2.0_Beta
source code, 3080K, uploaded Mar 28, 2008 - 5065 downloads

Release Notes

Please report any bugs and feature requests in the issue tracker**
/SingleSignOn/WorkItem/List.aspx

This is not a huge departure from what I had before, but it is significant enough that I decided to change the major version. This release will include a host of changes, bug fixes, and improvements. Please bare with me while I clean it up for a release. You can get the current code from the Source Code tab under the /trunk. I'll leave the old 1.1.0 release out here and you can see its source code under /tags/1.1.0 in the Source Code tab.

Changes include: {**Incomplete**}
*Server-side and client-side library separation - no more reference.cs file getting messed up when updating the web references
*Initialization handled using the built in initialization method. Now settings appear as attributes on the provider configuration vs a custom settings config section.
*numerous bug fixes that I've found by using this library.
*Synchronized my private library with the codeplex one. You get what I'm using.
*Built an optional Dynamic or Static service key. So now you can have a windows app that generates a key session and a web app that uses a static file.

Definitions:
Client-side is the web site or windows forms application that consumes these web services to access membership from a central server.
Server-side is the actual web site that hosts the web services providing the membership information.

Some caveats should be mentioned. This library is literally a passthrough to a server side membership provider. So any application using this shares its application name with the host application. Also, defining encryption, etc won't work because it relies on the server-side configuration for the SqlMembershipProvider. Since flat text is transmitted between the client applications and the server, you should use transport encryption (SSL/HTTPS) to protected your information. Also... all provider names server and client-side have to be the same name if you want to use the ASP.NET configuration tool on the client-side; I'll look into that so I can understand what's going on.

More documentation coming soon!

Source code includes Visual Studio 2005 and 2008 solutions

Stay tuned!

Reviews for this release

     
Trying to iplement this idea ;-)
by VijayKarla on Dec 4, 2008 at 1:40 PM