Document History

Date Author Description
20171222 Dave Boal Project Definition
20171223 Dave Boal In Progress: Database Documentation
20171228 Dave Boal In Progress: Authorization Flow Documentation
20180102 Dave Boal In Progress: Angular Login Documentation

Welcome to CodeQwik’s IdentityServer4 Adventures

IdentityServer4 (ID4) is an OpenID Connect and OAuth 2.0 framework written in ASP.NET Core 2.0…the docs are here.

The purpose of this site is to demonstrate how to implement both server-side and client-side ID4 Authentication, in several Client Applications, using various UI technologies. Hopefully this site will help other organizations extend their knowledge of Authentication using ID4.

PLEASE USE ANY AND ALL INFORMATION ON THIS SITE AT YOUR OWN RISK. NO SECURITY AUDITS HAVE BEEN PERFORMED, AND AT THIS VERY MOMENT, THIS DOCUMENT IS PROBABLY IN DRAFT FORM. WE INVITE YOU TO SUGGEST CORRECTIONS AS SOON AS WE GET OUR BLOG RUNNING AGAIN AT www.codeqwik.net.

The applications built will include the following:

Application Technology
Custom Implementation of IdentityServer4 Asp.Net Core 2.0
Login UI and User Manager Angular
User Profile UI Angular
User Profile UI ASP.Net MVC Core
User Profile UI ASP.Net WebForms
User Profile Web Service ASP.Net Core

The applications built will demonstrate the following ID4 Features:

Authentication as a Service

Centralized login logic and varying workflow for the following types of applications: Web UI (Angular.io, ASP.Net MVC, ASP.Net WebForms), Native Mobile (Xamarin), Web Services (ASP.Net Core).

Both Independent and Single Sign-on / Sign-out

Independent sign-on (and out) is when you login to a Browser app, and also have to login to a Xamarin Mobile App app even if you run them at the same time with the same user. Single sign-on (and out) allows you to login (and out) once over multiple application types. You sign-in to one, and you are signed in to them all.

Access Control for APIs by Client Application

Issue access tokens for APIs for various types of clients, e.g. server to server, web applications, SPAs and native/mobile apps.

Federation Gateway

Support for external identity providers like Azure Active Directory, Google, Facebook etc. This shields your applications from the details of how to connect to these external providers.