Comments by Bounze (Top 10 by date)

Thank you for your time in answering my question, Anvil! Please read below and thank you again for your time. I've replied to the one solution posted with more specific information.

Thank you very much for your time in answering my question, Dave!

Like you and the others have said: Bad idea on my part. Yet, my ultimate goal is to centralize all social network auth processes so that I don't have to code the same thing over and over when creating a new application. I was thinking about developing a Web Service that can do the job for my applications while maintaining a User and App credential database.

What brought me to the idea of sending a command to the remote computer to open the default browser, is the unfortunate fact that one of the first steps of authenticating users with a social network is to "navigate" them to the social network's login page and wait for a response from their server. This gave me the idea of simply handling that part on the consumer side and sending to the web service the result for parsing, evaluation and further action...Maybe I'm a little over my head.

So, what would you suggest as a correct approach to this issue and solution? what would you say would be a better idea for achieving the goal of centralizing all OAuth processes in only one place, so that no matter which of my apps want to authenticate they would go there instead of directly to the social network servers? Maybe try to implement this using ASP.NET, which includes Identity? What would you suggest?

Thank you!

Thank you very much for your input guys, very VERY glad to read your responses: Bad idea, so out the window it goes!

So in order to answer Sergey's statement, in the hopes that you guys can point me in the right direction...
My ultimate goal: To centralize all user authentication (specifically Social Network Authentication) processes in one Web Service, and not having different applications do their OAuth with these social networks (facebook, google, twitter, etc.) separately. That way, I can have all the OAuth flow for each service in a single solution (but with one Web Service/End Point each) and make it act as an intermediary between my apps and the social network oauth servers. My idea is that I can minimize coding by doing this because I don't have to program the oauth code each time I develop something new. My apps could all invoke this service which will take care of the flow and access a single database that manages these apps credentials with the social networks (app ids and secrets).

I think that explains it but let me know if I wasn't clear on something.

Thanks!!! :-)

Hi, j snooze! And thank you so much for your comment! Actually, I do understand that using a console app will be more work than to write 3 lines of code ;) hahahaah I have been investigating the code in the default template when you create a ASP MVC new project in VS. I do understand that everything is practically built in there and works beautifully; you just have to de-comment the code for the provider you wish to use (google, facebook, etc.) The problem is that in my specific situation, doing this by browser is not an option. Therefore, I understand that I would have to build the flow manually, but since I'm new to C# and ASP.Net MVC, I've been trying to "decipher" all the code in the default template so that I can understand what goes on and then figure out how to build my solution in a console or windows application from scratch using the concepts and object in the template: LOTS OF WORK. What I'm really looking for is a sort of TUTORIAL that can explain, in plain and simple words (like for beginners), the scenario: which elements/objects are needed for the whole thing to work and how to use them in C#.

Thanks a BUNCH for your time and care in answering my problem! :-D

Yes, and here's what they say about showing code-specific examples:
"Because of the various combinations of code languages that could be used in web apps, our guide doesn't show specific examples. However most modern languages will be capable of URL parsing..."
Apparently they feel like they would be sending a wrong message if they post examples using one language in particular...or something like that. But thank you for your suggestion, although I've been all over that site looking for help already ;-)