The identityserver4demo from proudmonkey

identityserver4demo's Introduction

Hi there 👋

I'm Vince and I work as a Solutions Architect. I’m very passionate about learning new technologies and ideas, I enjoy tackling challenges and sharing what I learned in the technical community through writing articles, books and answering to forums. I have over 18 years of software engineering experience - years of making mistakes and learning from them. 11-time Microsoft MVP, 5-time C# Corner MVP, CodeProject MVP, MVA, MVA, OSS Contributor, Microsoft Influencer, DZone MVB and a regular contributor at various online technical communities.

Microsoft MVP | CodeProject MVP | CodeProject MVA | CodeProject MVE | CsharpCorner MVP

📝 I write technical articles related to ASP.NET CORE, .NET 5 and Azure on my blog. Feel free to subscribe and get the latest posts delivered right to your inbox!
🔭 I’m currently working on a new open-source project template for ASP.NET Core APIs. Stay tuned!
📘 The recent book that I coauthored is out. Check it out here: ASP.NET Core 5 for Beginners.
☁️ I’m currently learning Azure and Cloud stuff.
🐦 Follow me on twitter @vmsdurano
🔗 Let's connect on linkedin
🏫 I'm an All-Star member at Microsoft ASP.NET forums (100k+ rep), Legend member at CodeProject (72k+ rep) and Platinum member at C# Corner (15k+ rep)

📚 Books written:

identityserver4demo's People

Contributors

Stargazers

Watchers

identityserver4demo's Issues

Breaks with the latest version of Identity Server 4

Hi,

Great demo but it breaks once you update Identity Server to latest version, ApiResource more specifically.

Thanks.

Migration steps to v4
As described above, starting with v4, scopes have their own definition and can optionally be referenced by resources. Before v4, scopes where always contained within a resource.

To migrate to v4 you need to split up scope and resource registration, typically by first registering all your scopes (e.g. using the AddInMemoryApiScopes method), and then register the API resources (if any) afterwards. The API resources will then reference the prior registered scopes by name.

Incorrect port

Thanks for all your work on the API boilerplate and the IdentityServer4 Demo - both are excellent. In your latest code updates, in WeatherApi\startup.cs:

services.AddAuthentication(IdentityServerAuthenticationDefaults.AuthenticationScheme)
.AddIdentityServerAuthentication(options =>
{
options.Authority = "https://localhost:44354";
options.ApiName = "app.api.weather";
});

in my case, should be:

It might help to comment the above hardcoded port that it needs to be changed to match the ssl port of the TokenServer's launchSettings.json "sslPort" setting. Even better, an appsettings.Development.json configuration entry could be helpful.

Recommend Projects

proudmonkey / identityserver4demo Goto Github PK

identityserver4demo's Introduction

Hi there 👋

identityserver4demo's People

Contributors

Stargazers

Watchers

Forkers

identityserver4demo's Issues

Breaks with the latest version of Identity Server 4

Incorrect port

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent