Jul 24, 2011 11:53 PM|magicmike2011|LINK
![]() Re: social networking website
Well... I am aware of a few options, it just depends on what you're willing to work with...
Any of the ones I know of are pretty much proprietary of their own code (meaning it's a pain in the @** to mess with their code to customise it to your needs).
One is Active Social, it is DotNetNuke platform which is .NET based and would work with an asp.net structure with some playing around. I don't recall active social being free though. I'm pretty sure it was something liek 'here, you can have the basic module, but you have to buy the modules that actually make it functionally useful..' lol
C#.Net Projects – Free Downloads with Source Code and Project Report. ASP.Net Projects – Free Downloads with Source Code and Documentation.
Another is Vivo Social which I believe is DDN based aswell, but don't qoute me. It is also completely open source (surprisingly, given its vast scope of features). It is, however, not overly proprietary in code, and is very easily customizable in asp.net. I will give you this warning though.... The site it's self that developed it is a MESS to try to find info from. Basicaly, if you knwo what your doing, just load up the solution in VWD or whatever environment you develop in and have at it yourself lol. (yes the help info on their site is THAT bad... lol)
Also to note, DotNetNuke does have a bajillion free modules made by the community which if pieced together properly could provide the foundation you might be looking for.
As for a plain and simple asp.net social site starter kit... you probably won't have much luck :( atleast not microsoft developed anyway.
The problem using a starter kit for a social site is that social sites have such a massive possibility of features that a developer might want to implement. They are so diverse in nature. And when you use a starter kit, although it may appear to save some time, you can almost guarantee it wont have all the features you need/want. Then you have to have to try to work those features into it yourself the old fashion way, and like I said, most social site kits are EXTREMELY proprietary (and usually costly).
My personal opinion (ooonly an opinion ) is that teh best way is to build it from teh ground up yourself. That way you fully understand the structure and functionality, and you get exactly what you want. And who doesn't like getting what they want?
Also just an observation.. WOW does this thread have a lot of views!!!
Hopefully this helps
-->
By Valeriy Novytskyy and Rick Anderson
This tutorial demonstrates how to build an ASP.NET Core 3.0 app that enables users to sign in using OAuth 2.0 with credentials from external authentication providers.
Facebook, Twitter, Google, and Microsoft providers are covered in the following sections and use the starter project created in this article. Other providers are available in third-party packages such as AspNet.Security.OAuth.Providers and AspNet.Security.OpenId.Providers.
Enabling users to sign in with their existing credentials:
For examples of how social logins can drive traffic and customer conversions, see case studies by Facebook and Twitter.
Create a New ASP.NET Core Project
Apply migrations
Forward request information with a proxy or load balancer
If the app is deployed behind a proxy server or load balancer, some of the original request information might be forwarded to the app in request headers. This information usually includes the secure request scheme (
https ), host, and client IP address. Apps don't automatically read these request headers to discover and use the original request information.
The scheme is used in link generation that affects the authentication flow with external providers. Losing the secure scheme (
https ) results in the app generating incorrect insecure redirect URLs.
Use Forwarded Headers Middleware to make the original request information available to the app for request processing.
For more information, see Configure ASP.NET Core to work with proxy servers and load balancers.
Use SecretManager to store tokens assigned by login providers
Social login providers assign Application Id and Application Secret tokens during the registration process. The exact token names vary by provider. These tokens represent the credentials your app uses to access their API. The tokens constitute the 'secrets' that can be linked to your app configuration with the help of Secret Manager. Secret Manager is a more secure alternative to storing the tokens in a configuration file, such as appsettings.json.
Important
Secret Manager is for development purposes only. You can store and protect Azure test and production secrets with the Azure Key Vault configuration provider.
Follow the steps in Safe storage of app secrets in development in ASP.NET Core topic to store tokens assigned by each login provider below.
![]() Setup login providers required by your application
Use the following topics to configure your application to use the respective providers:
Multiple authentication providers
When the app requires multiple providers, chain the provider extension methods behind AddAuthentication:
Optionally set password
When you register with an external login provider, you don't have a password registered with the app. This alleviates you from creating and remembering a password for the site, but it also makes you dependent on the external login provider. If the external login provider is unavailable, you won't be able to sign in to the web site.
To create a password and sign in using your email that you set during the sign in process with external providers:
Next steps
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |