Skip to content
This repository was archived by the owner on Apr 27, 2021. It is now read-only.
michael.vidal edited this page Aug 11, 2017 · 8 revisions

What is Fabric.Identity?

Fabric.Identity is a service that provides centralized authentication and authorization for health care applications and apis that want to participate in the Fabric ecosystem.

What is Fabric?

Fabric is a set of micro-services for healthcare. You can pick and choose only the services you want and install them via docker.

What problem does Fabric.Identity solve?

By leveraging OpenID Connect via IdentityServer4, Fabric.Identity allows developers of health care applications the ability to offload authentication of users in their application to Fabric.Identity. This enables developers to concentrate on delivering business value rather than spending time building secure authentication mechanisms.

Fabric.Identity also allows developers to easily add authorization to their APIs, and make them accessible as services in the larger Fabric ecosystem.

Check out our Getting Started page to start using Fabric.Identity today.

How does Fabric.Identity work?

Essentially, Fabric.Identity is an OpenID Connect server that serves as an abstraction over other Identity Providers like Active Directory, Azure Active Directory, Google Authentication, etc...

This abstraction allows applications that want to participate in the Fabric ecosystem the ability to integrate with Fabric.Identity for authentication, and not have to worry about disparate authentication mechanisms throughout (and sometimes within) various enterprises. Developers need to only know how to work with the OpenID Connect specification exposed by Fabric.Identity.

Clone this wiki locally