The WIF framework provides a basic programming model for claim-based authentication. I have already implemented this step over here Configuring ADFS in Azure Virtual Machine.
It includes a serialized copy of the issuer’s certificate that provides your application with the correct public key to verify incoming tokens.Now ADFS needs to know a few things about an application before it can issue it any tokens.These questions include information related to URI of the application, which claims are required by applications out of issue by ADFS, URL of the application to receive tokens and so on.Fill in the details in the “General” tab as shown in the following screenshot. Click Next to continue and then click on Finish to complete the new user creation procedure.Now we will add another user in the same active directory. First let me show how you can locate the metadata URL of your ADFS and in the next section, we will explore the why part of it.
Single page application in asp.net mvc 4
Active Directory Federations Services (ADFS) is an enterprise-level identity and access management service provided by Microsoft.ADFS runs as a separate service and hence any application that supports WF-Federation and Security Assertion Markup Language (SAML), can leverage this federation authentication service.Once you have developed a claim-based application using WIF and have used ADFS to issue security token, the next step is to set up a trust relationship. An application needs to trust the ADFS to identify and authenticate users and make claims about their identities.When you configure an application to rely on a specific issuer, you are establishing a TRUST (or TRUST RELATIONSHIP) with that issuer.WIF includes a wizard that automatically configures application’s identity settings based on this metadata.