Umbraco is an open source .NET based content management system. It is released under the MIT license and powers a number of high profile sites, most notably Microsoft's own www.asp.net website.
- Stackoverflow.com Wiki
Say for example you have a CMS :) You want to give full control to the developer to manage how their front-end members with authenticate, which could of course include ASP.Net Identity OAuth login providers. At the same time you want to easily allow your CMS to be configured so that ASP.Net Identity OAuth providers can be used for logging into the back office.
Starting a new project can sometimes be fun and easy, sometimes the sheer size and complexity of what’s being asked can be quite daunting. In today’s guide, I’m going to cover my rough thought process when it comes to planning out a new project.
If you're used to working with Umbraco, you're probably also familiar with with the various sections of Umbraco - e.g. Content and Media for the editors, or Developer and Settings for the developers. If you need something more than what Umbraco gives you by default, you can also add your own section - which is what this article is about.
The Umbraco REST API package, installed as a DLL in an Umbraco project it allows you (with some minimal configuration) to expose several REST API endpoints which allow CRUD (Create, read, update, delete) of Members, Content, Relations and Media.
Restricting access to a clients website can be a common practice. This usually means that they will need to have access give to an IP address or a range of IP addresses.