From b76a6858f3b23faa00a6ddafeb9b4e30927ead21 Mon Sep 17 00:00:00 2001 From: Nate Barbettini Date: Fri, 21 Dec 2018 08:21:42 -0800 Subject: [PATCH] Update README.md --- okta-hosted-login/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/okta-hosted-login/README.md b/okta-hosted-login/README.md index e31cd98..1e091d3 100644 --- a/okta-hosted-login/README.md +++ b/okta-hosted-login/README.md @@ -67,6 +67,7 @@ If you were able to successfully login in the previous section you can continue * [Node/Express Resource Server Example](https://github.com/okta/samples-nodejs-express-4/tree/master/resource-server) * [Java/Spring MVC Resource Server Example](https://github.com/okta/samples-java-spring-mvc/tree/master/resource-server) +* [ASP.NET](https://github.com/okta/samples-aspnet/tree/master/resource-server) and [ASP.NET Core](https://github.com/okta/samples-aspnetcore/tree/master/resource-server) Resource Server Examples Once you have the resource server running (it will run on port 8000) you can visit the `/messages` page within the Angular application to see the authentication flow. The Angular application will use its stored access token to authenticate itself with the resource server, you will see this as the `Authorization: Bearer ` header on the request if you inspect the network traffic in the browser.