The Fabric.Identity service provides centralized authentication across the Fabric ecosystem. The goal is to allow client applications (aka relying party applications) the ability to offload authentication logic to Fabric.Identity so that developers of the client applications can concentrate on solving their core business needs and not have to build one off authentication systems. Fabric.Identity is based on the OpenID Connect specification and leverages IdentityServer4 as the OpenID Connect provider implemenation.
The Fabric.Identity service is built using:
- ASP .NET Core 1.1
- IdentityServer4
The documentation on our Getting Started page will show you how to quickly get Fabric.Identity running in Docker and start developing an application using Fabric.Identity as your authentication mechanism.
If you would like to build from source without using a Docker image follow the instructions below:
- Install .NET Core 1.1
- Clone or download the repo
- Launch a command prompt or powershell window and change directory to the Fabric.Identity.API directory and execute the following commands
dotnet restoredotnet run
Fabric.Identity service will start up and listen on port 5001.
You can run the following curl commands to ensure the service is up and working properly:
curl -G http://localhost:5001/.well-known/openid-configuration
Which will return a json document representing the discovery information for the service:
{
"issuer": "http://localhost:5001",
"jwks_uri": "http://localhost:5001/.well-known/openid-configuration/jwks",
"authorization_endpoint": "http://localhost:5001/connect/authorize",
...
}
You can then run the setup-samples.sh script to setup the sample applications in Fabric.Identity.