SingleSignOn Wiki & Documentation Rss Feed

Updated Wiki: Home

nlb6665 — Tue, 08 Sep 2009 14:18:11 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 Apr 2008 23:29:20 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 Apr 2008 23:29:00 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 Apr 2008 23:28:36 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 Apr 2008 22:49:16 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 Apr 2008 22:48:55 GMT

Project Description
In short, this is simply a pass-through web service membership provider and role provider library. I've taken advantage of the 2.0 membership provider model to allow pre-existing applications to easily integrate this library. The idea is to have one centrally hosted asp.net web application containing all the user accounts that will be shared among many other applications and provide a web service for those applications to use its authentication functions. The download includes: a sample host server, provider client libraries, sample web client, and sample windows client.

Donations
I have gotten a few requests about donations to the project. Feel free to click this link an contribute any amount you wish. We greatly appreciate your support.
{"<form action="https://www.paypal.com/cgi-bin/webscr" method="post">
<input type="hidden" name="cmd" value="_s-xclick">
<input type="image" src="https://www.paypal.com/enUS/i/btn/btndonate_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1">
<input type="hidden" name="encrypted" value="-----BEGIN PKCS7-----MIIHVwYJKoZIhvcNAQcEoIIHSDCCB0QCAQExggEwMIIBLAIBADCBlDCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20CAQAwDQYJKoZIhvcNAQEBBQAEgYA0yXSdeJMuFRBN844nzcq1FtHpwsv9eheU5pF8883n0J8MiI/PsMvMX5rmQlH4IdkCYejvMEyz898pH9q4NXVblhbH/aBExD5Vmtgn1EC0ByQtlTdw0hTd8OvFwNuTTC82tVNRBAiHy1kRwSfyHM4dPAZQdR4PfU659wERrbzELMAkGBSsOAwIaBQAwgdQGCSqGSIb3DQEHATAUBggqhkiG9w0DBwQIaSob23g3sRGAgbBFN3DLSauz4cqrdJRtAgxZC6cyOTZ/2smYCsY0UbXDayKQ1ZrDx3dVxILeAPngsRt5zCz53oNfoCVsywvs4PovHV3Wig7tA7i9qODHzfqtvTcv2YyLqrEN6JyRnuuCcsX27DIv/K9SWGB4JO/cPzFZOexhmjpPiIqMHGHmhdbkAooXCE78sPk89I42BvqhCaOYEPokTcbJTSNNfbEEAJ6JppeJAihS5l9HMa1DwzSaCCA4cwggODMIIC7KADAgECAgEAMA0GCSqGSIb3DQEBBQUAMIGOMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFjAUBgNVBAcTDU1vdW50YWluIFZpZXcxFDASBgNVBAoTC1BheVBhbCBJbmMuMRMwEQYDVQQLFApsaXZlX2NlcnRzMREwDwYDVQQDFAhsaXZlX2FwaTEcMBoGCSqGSIb3DQEJARYNcmVAcGF5cGFsLmNvbTAeFw0wNDAyMTMxMDEzMTVaFw0zNTAyMTMxMDEzMTVaMIGOMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFjAUBgNVBAcTDU1vdW50YWluIFZpZXcxFDASBgNVBAoTC1BheVBhbCBJbmMuMRMwEQYDVQQLFApsaXZlX2NlcnRzMREwDwYDVQQDFAhsaXZlX2FwaTEcMBoGCSqGSIb3DQEJARYNcmVAcGF5cGFsLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAwUdO3fxEzEtcnI7ZKZL412XvZPugoni7i7D7prCe0AtaHTc97CYgm7NsAtJyxNLixmhLV8pyIEaiHXWAh8fPKWR017EmXrr9EaquPmsVvTywAAE1PMNOKqo2kl4Gxiz9zZqIajOm1fZGWcGS0f5JQ2kBqNbvbg2/ZaGJ/qwUCAwEAAaOB7jCB6zAdBgNVHQ4EFgQUlp98u8ZvF71ZP1LXChvsENZklGswgbsGA1UdIwSBszCBsIAUlp98u8ZvF71ZP1LXChvsENZklGuhgZSkgZEwgY4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEWMBQGA1UEBxMNTW91bnRhaW4gVmlldzEUMBIGA1UEChMLUGF5UGFsIEluYy4xEzARBgNVBAsUCmxpdmVfY2VydHMxETAPBgNVBAMUCGxpdmVfYXBpMRwwGgYJKoZIhvcNAQkBFg1yZUBwYXlwYWwuY29tggEAMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADgYEAgV86VpqAWuXvX6Oro4qJ1tYVIT5DgWpE692Ag422H7yRIr/9j/iKG4Thia/Oflx4TdLIFJBAyPK9v6zZNZtBgPBynXb048hsP16l2vi0k5Q2JKiPDsEfBhGIHnxLXEaUWAcVfCsQFvd2A1sxRr67ip5y2wwBelUecP3AjJYcxggGaMIIBlgIBATCBlDCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20CAQAwCQYFKw4DAhoFAKBdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA4MDQyOTIyNDYwN1owIwYJKoZIhvcNAQkEMRYEFDIJrm1wZXmabk1v2tyPIFC56dCMA0GCSqGSIb3DQEBAQUABIGAbehytPwxXbsgov0aGbGoBQ1EEgImIbHe/LHvpxBrPqn0Hkt4EwPKHhIbxcV2VrUU22B4ISxQCbv8e5ElVFkQoHvVh162c4VZ9bdJUdAKd24efVVcAO4wwWDxhcLnseR8ILNEsyxGZWsxlMDJBBQ2jb+SLUExLzCtlQeWdyDSA=-----END PKCS7-----
">
</form>"}

Notes
Originally I built this application to be the central authentication system of about ten or so in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using .NET 1.0 and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Thanks to the guys working on SubSonic! I used SubSonic for my data access layer in these projects.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Here's a diagram showing the basic application architecture of this solution.

UPDATED WIKI: Home

nlb6665 — Sat, 29 Mar 2008 06:54:42 GMT

UPDATED WIKI: Home

nlb6665 — Fri, 28 Mar 2008 05:30:59 GMT

UPDATED WIKI: Home

nlb6665 — Fri, 28 Mar 2008 05:30:44 GMT

UPDATED WIKI: Home

papab30 — Thu, 05 Jul 2007 15:58:23 GMT

Project Description
This is a set of code projects that allow a developer to use built-in 2.0 membership provider features and connect multiple applications (web and windows) to the same user base via web services hosted on the Internet or intranet. Project includes host server, client libraries, sample web client, and sample windows client.

Notes
Originally I built this application to be the central authentication system of about ten or so in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using .NET 1.0 and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Here's a diagram showing the basic application architecture of this solution.

UPDATED WIKI: Home

nlb6665 — Mon, 18 Jun 2007 17:56:45 GMT

Project Description
This is a set of code projects that allow a developer to use built-in 2.0 membership provider features and connect multiple applications (web and windows) to the same user base via web services hosted on the Internet or intranet. Project includes host server, client libraries, sample web client, and sample windows client.

Notes
Originally I built this application to be the central authentication system of about ten or more other in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using .NET 1.0 and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Here's a diagram showing the basic application architecture of this solution.

UPDATED WIKI: Home

nlb6665 — Fri, 15 Jun 2007 20:59:08 GMT

Project Description
This is a set of code projects that allow a developer to use built-in 2.0 membership provider features and connect multiple applications (web and windows) to the same user base via web services hosted on the Internet or intranet. Project includes host server, client libraries, sample web client, and sample windows client.

Notes
Originally I built this application to be the central authentication system of about ten or more other in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using .NET 1.0 and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Here's a diagram showing the basic application architecture of this solution.

UPDATED WIKI: Home

nlb6665 — Fri, 15 Jun 2007 18:56:24 GMT

Project Description
This is a set of code projects that allow a developer to use built-in 2.0 membership provider features and connect multiple applications (web and windows) to the same user base via web services hosted on the Internet or intranet. Project includes host server, client libraries, sample web client, and sample windows client.

Notes
Originally I built this application to be the central authentication system of about ten or more other in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using .NET 1.0 and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Here's a diagram showing the basic application architecture of this solution.

Thanks!
-Nathan

UPDATED WIKI: Home

papab30 — Mon, 04 Jun 2007 15:41:02 GMT

Project Description
This is a set of code projects that allow a developer to use built-in 2.0 membership provider features and connect multiple applications (web and windows) to the same user base via web services hosted on the Internet or intranet. Project includes host server, client libraries, sample web client, and sample windows client.

Notes
Originally I built this application to be the central authentication system of about ten or more other in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using .NET 1.0 and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Thanks!
-Nathan

UPDATED WIKI: Home

nlb6665 — Sun, 03 Jun 2007 01:48:45 GMT

Project Description
This is a set of code projects that allow a developer to use built-in 2.0 membership provider features and connect multiple applications (web and windows) to the same user base via web services hosted on the Internet or intranet. Project includes host server, client libraries, sample web client, and sample windows client.

Notes
Originally I built this application to be the central authentication system of about ten or more other in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using 1.0 .NET and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Thanks!
-Nathan

UPDATED WIKI: Home

nlb6665 — Tue, 29 May 2007 21:14:38 GMT

Project Description
This is a set of code projects that allow a developer to use built-in 2.0 membership provider features and connect multiple applications (web and windows) to the same user base via web services hosted on the Internet or intranet. Project includes host server, client libraries, sample web client, and sample windows client.

Notice
For the next few days I'm going to be posting minor changes here and there to get this project up to par with its initial state. It's still missing a few items like install docs and a sample windows client project. A release build will come as soon as these items are complete.

Notes
Originally I built this application to be the central authentication system of about ten or more other in-house applications. All these ran on a local intranet, and I was tired of handing out ten usernames and passwords for each person to login to each application, so I designed a system similar to this one (using 1.0 .NET and web services). The solution worked great for our local and remote users.

So now I've designed a new set of applications taking advantage of the built-in membership provider model and web services in .NET 2.0. The idea is to link all your internal .net driven applications to authenticate with one system and allow remote users use the same user base. It's geared for web applications, but can be used for windows desktop applications with access to the host web services.

Beta Testers and feedback are welcome. I'd like to hear what people have to say. Is this something you can use? If someone already has something like this, how does it compare? etc.

Thanks!
-Nathan

UPDATED WIKI: Home

nlb6665 — Tue, 29 May 2007 19:55:58 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 May 2007 19:54:41 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 May 2007 19:27:50 GMT

UPDATED WIKI: Home

nlb6665 — Tue, 29 May 2007 19:26:03 GMT