https://github.com/mikoskinen/OcelotIdentityServerAzureAdWithApi

Demo for a scenario where API is accessed through Ocelot gateway and Ocelot uses IdentityServer and Azure Ad for authentication
https://github.com/mikoskinen/OcelotIdentityServerAzureAdWithApi

Last synced: 3 months ago
JSON representation

Demo for a scenario where API is accessed through Ocelot gateway and Ocelot uses IdentityServer and Azure Ad for authentication

• Host: GitHub
• URL: https://github.com/mikoskinen/OcelotIdentityServerAzureAdWithApi
• Owner: mikoskinen
• Created: 2019-12-10T12:20:44.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2021-08-25T14:58:15.000Z (over 3 years ago)
• Last Synced: 2024-10-05T08:41:13.845Z (4 months ago)
• Language: C#
• Size: 1.28 MB
• Stars: 3
• Watchers: 1
• Forks: 4
• Open Issues: 2
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

• awesome-ocelot - Demo for a scenario where API is accessed through Ocelot gateway and Ocelot uses IdentityServer and Azure Ad for authentication

README

        
# Ocelot & IdentityServer & AzureAD

Demo for a scenario where the following tools are used:

* Ocelot Gateway (Gateway.sln)

* Microservices behind the Ocelot Gateway (Microservices.sln)

* Website in front of the Ocelot Gateway (MvcTestSite.sln) 

* IdentityServer (IdentityServer.sln)

* Azure AD

Requires .NET Core SDK 3.1.100.

The following services are behind the Ocelot:

* Microservice1

* Microservice2

* SuperMicroservice

* IdentityServer

MvcTestsite sits in front of the Gateway.

![Architecture diagram](diagram.png)

## Permissions

By default the following permissions are applied:

* Microservice1 can call Microservice2 but not SuperMicroservice.

* Microservice2 can call Microservice1 but not SuperMicroservice.

* SuperMicroservice can call Microservice1 and Microservice2.

* MvcTestSite's client can call Microservice1 and Microservice2 but not SuperMicroservice.

* MvcTestSite's Azure AD signed user can call Microservice1, Microservice2 and SuperMicroservice.

## Testing

Use *MvcTestSite* to test microservices calling each other. The same site can be used to test Azure Ad sign-in and the calling of a microservice through the gateway.

Run the solutions in the following order:

1. Microservices (should start Microservice1, Microservice2 and SuperMicroservice in the following ports: 44392, 44393, 44394)

2. Gateway (https://localhost:44334/)

3. IdentityServer (http://localhost:5000/)

4. MvcTestSite (https://localhost:44322/)

Use "Privacy"-page to sign-in with Azure AD and to call the SuperMicroservice.

## Azure Ad configuration

Create a new Azure AD app registration:

![](azuread.png)

Copy the Azure Ad application settings to IdentityServer/Startup.cs.