There are few breaking changes in Asp.Net Core Identity in net core 2.0. One of the major change is removing navigation properties from Identity entities like IdentityUser, IdentityRole.
Recently I need to simulate production environment (in a case of secure connection) to check application behavior so I quickly searched Asp.Net Core docs and find this article. I followed IIS Express approach, once I finished setup and tried to run the application then I ran into an issue on Chrome and Firefox but OK with Edge. That’s strange and based on the error shown by chrome I was guessing this is not application fault but something wrong with browsers.
Recently I was trying to build a multi-tenant application using Asp.Net Core. In that journey, I found an amazing series by Ben Foster where he wrote step by step guide to building multi-tenant application with Asp.Net Core and SaaSKit (A developer toolkit for building SaaS applications). With the help of that series, I am able to build foundation for multi-tenant application. I have added a bit more features in my sample like creating a database per tenant as they loaded the first time. I have shared my multi-tenant foundation application in GitHub so that other can get an idea to build their own. I will add more features along the way.
Recently I was working on a project where I have to build simple Authentication Server. For that project, i need to use Resource Owner Password (ROP) OAuth flow with persistence storage of all data. Also, need to handle Social Signup/login with ROP flow. Facebook and Google as third party Identity Provider is available in this sample ( up to now)
So I am using Identity Server 4 and Entity Framework core to build this simple authentication server. This sample might be helpful if you are working on same as my requirement.
Also, I am extending this sample to support other OAuth flow in future.
Here is project link in Github.
In the first post, I talked about MongoDB briefly and showed how to set up a local environment to work with MongoDB.
In this second post, I will show you how to actually use MongoDB as a data storage with ASP.NET Core application with simple CRUD operation. As I mentioned earlier I am using ASP.NET Core Web API for this article.
In this 2 part series, I will show you how to use MongoDB as data storage in your ASP.NET Core application.
As you may know, MongoDB is an open-source document database and leading NoSQL database. It is a cross-platform, document oriented database that provides, high performance, high availability, and easy scalability. MongoDB works on the concept of collection and document.
In this post, I will guide you on how to add Azure AD as an identity provider in your ASP.NET Core application. We will use OpenId Connect middleware to sign in users from an Azure Active Directory tenant.
First let’s know a bit about JSON Patch.
JSON Patch is a format (identified by the media type “application/json-patch+json”) for expressing a sequence of operations to apply to a target JSON document; it is suitable for use with the HTTP PATCH method.
Asp.Net Core 1.1 now provides GZip Compression middleware. GZip is a method of compressing files (making them smaller) for faster network transfers. Compression allows your web server to provide smaller files sizes which load faster for your users.
Currently i am developing a simple web application (my side project https://test-api.net/) where developers can get mock API for test purpose and i want to set up login feature but i don’t want to put classical username/password so i was searching for suitable login provider where most of developer hang around and came up with GitHub as login provider because this is a place where developer hang around most and it will be easy to use as a login provider.