social-login

ASP.NET MVC & Social Login Example

This example shows you how to use the Okta.AspNet library to log in a user via other identity providers such as Google or Facebook. The user's browser is first redirected to the self-hosted login page on your ASP.NET MVC application with multiple login options. Once the user is successfully authenticated, ASP.NET MVC automatically populates HttpContext.User with the information that the identity provider sends back about the user.

Prerequisites

Before running this sample, you will need the following:

• An Okta Developer Account, you can sign up for one at https://developer.okta.com/signup/.
• An Okta Application, configured for Web mode. This is done from the Okta Developer Console and you can find instructions here. When following the wizard, use the default properties. They are designed to work with our sample applications.
• The desired identity providers configured in Okta. This is done from the Okta Developer Console and you can find instructions here.

Note: Make sure to add https://localhost:44314 as a Trusted Origin.

Running This Example

Clone this repo and replace the okta configuration placeholders in the Web.Config with your configuration values from the Okta Developer Console. You can see all the available configuration options in the okta-aspnet GitHub.

Now start your server and navigate to https://localhost:44314 in your browser.

If you see a home page that allows you to log in, then things are working! Clicking the Log in link will redirect you to the self-hosted sign-in page with multiple sign-in options.

If you want to log in via Okta, you can log in with the same account that you created when signing up for your Developer Org, or you can use a known username and password from your Okta Directory.

Notes: If you are currently using your Developer Console, you already have a Single Sign-On (SSO) session for your Org. When you log in via Okta, you will be automatically logged into your application as the same user that is using the Developer Console. You may want to use an incognito tab to test the flow from a blank slate.

Because of recent changes in Set-Cookie behavior (SameSite) this code will only work properly if it's configured to use https. Check out Work with SameSite cookies in ASP.NET for more details.