I'm currently working with a asp.net MVC5 project. But I had a fun Idea I would made a WPF application aswell. And with this WPF application I would like to login with the login info I have on my asp.net site. I do know how to link the database to my WPF application how ever, after doing this I am stuck and I would appricate some help.
This is already provided by the ASP.NET Client Application Services, which expose ASP.NET services like membership, profile etc as services to other applications. Authentication is specifically addressed in How to: Implement User Login with Client Application Services with a full walkthrough in Walkthrough: Using Client Application Services.
A far better solution though would be to use Windows Authentication, if the WPF client and IIS servers are in the same domain. This way you wouldn't need to do anything on the client side, and only have to enable Windows Authentication on the server side.
Related
I have implemented a login system in my MVC web application using ASP Identity framework with owin. In addition to that, I need to integrate Central Authentication Service (CAS) into my login system as an external login mechanism.
All tutorials I found was only using CAS. Is there any way I could accomplish that?
First off, I'm completely new to Shibboleth and SAML. We have a ..net web application which uses the .net membership provider functionality for forms authentication. We need to keep the .net mode of authenticating. However, we've now been asked to add the ability to authenticate a user coming from another web application which uses Shibboleth.
My question is, and I apologize if it sounds stupid, but can a .net web application implement both the 'default' asp membership and shibboleth authentication, or does it have to be one or the other?
Our web app is a .net 4.5 written in vb.net and hosted on Windows server. The other is a web app written in PHP (if I'm not mistaken) uses Shibboleth and is on a Linux server.
Thanks!
I have been tasked to set up Single Signon for asp.net application (SAAS) using IIS server with a client who has ADFS3.0 for providing identity credentials. the users authenticated will be allowed to log in to the web application but i have been going through a lot of information as how to set up service provider files as the application is already running.
what settings and where do i need to configure them. any help will be greatly appreciated.
The "modern" way to do this is by using OWIN.
You will have to change your application as per Use the OWIN Security Components in ASP.NET to Implement Web Sign On with ADFS.
Then add your RP to ADFS and you are good to go.
For completeness. the "old" way to do this is to use WIF as in How To: Build Claims-Aware ASP.NET MVC Web Application Using WIF.
I am starting a new MVC project for one of my clients. They already have an iPhone app which is having most of the functionalities that I intend to do. And a web service exists. I do not have any database side work. My question is, I want to use the web service calls for authentication. But asp.net MVC is using Identity as default authentication. How do I tackle to use Identity with out much effort to call the web service for authentication?
I have a winforms application which calls web services and then based on the results fires up an ASP.NET webpage.
The ASP.NET webpage and web services are protected by a custom membership provider. At present the user has to log in to their winforms app and then also into the asp.net webpage. Is there a way to only have to log in to the winforms app and somehow share whatever authentication state exists with the ASP.NET webpage?
I've seen http://msdn.microsoft.com/en-us/library/vstudio/eb0zx8fc(v=vs.85).aspx - however it seems to be more aimed at sharing authentication between server applications, not two client applications.