Last post Sep 14, 2017 08:52 AM by Edward Z
Sep 08, 2017 02:59 PM|JamesFJr|LINK
So I watch a great plural site video (Understanding ASP.NET Core Security by Roland Guijt) and read and study tutorials by the masters of Identity Server, Brock Allen & Dominick Baier. I felt confident and ready to proceed with my cutting edge Azure Application.
After a few false starts and fundamental changes, I manage to get an almost working Identity Server, Internal API and a Web Application Client. I tell my boss it's only a matter of time before we can dump that nasty node/angular solution and the third party
token service. Then to my surprise, there is an upgrade to most of the Microsoft Nuget packages to .NET Core 2.0. I think that it couldn't be better timing and that my solution will be that much better and even more cutting edge and impressive than originally
I should have known better by now, but my application becomes inoperable and I find much of my startup code has now become obsolete or no longer works. Yet, with an optimistic attitude I seek out those reliable sources of code changes and to my ultimate
dismay, these are vague and don't seem to fit my scenario, which I thought was very standard practice.
What's more, I cannot seem to find any up-to-date tutorials or instructions on how to fix my application and properly register my client web application and set my API resource correctly in the Identity server as well as in its own startup.
Anyway, if you decided not to waste your time with the above story of my troubles in ASP.NET core land, can someone just provide some resources or direction where I could turn to help guide me through these changes. I know there is a page out there (https://github.com/aspnet/Announcements/issues/262
) which is supposed to be crystal clear and should be more than adequate for someone with my intelligence and experience to follow along and clear up my issues. However, I find it very vague and severely lacking in clear instruction on how to get my solution
working again, even after reading and rereading its contents.
So I will be forever in your debt and your best friend if you can provide any good reference which might explain or better yet demonstrate how to update my code to operate within the confines of the changes that ASP.NET Core 2.0 has imposed on us loyal Microsoft
Azure Web Solution designers and our standard Web, API, Identity Server solutions.
Thank you so very much in advance.
Sep 14, 2017 08:52 AM|Edward Z|LINK
Do you mean you want to achieve IdentityServer4 in Asp.Net Core 2.0? It seems the issue has been fixed on 2.0.0-preview4, I suggest you check below issue.
# Support ASP.NET Core 2.0 #1055
As the comment from brockallen, you could append comment on below issue if there is any error using IdentityServer4 in Core 2.0
# 2.0 breaking changes list #1057