Creating openid connect authentication/authorization is just a struggle with your docs

[shoter]

This sentence

When you use this workflow, the ASP.NET Core Identity middleware is not needed, because all user information storage and authentication is handled by the Identity service.

It's hard to make out what you really mean for someone configuring everything for the first time. Do I need to remove some code connected with Identity? First thing that comes into mind is to remove:

            services.AddDefaultIdentity<IdentityUser>(options => options.SignIn.RequireConfirmedAccount = false)
                .AddEntityFrameworkStores<ApplicationDbContext>();

But it is not middleware. As a reader I am just confused what you want to tell me. Example project with some setup would be greatly appreciated.

Even example code to see what I need to remove would be great.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d926868f-5446-63c6-75c0-ba879879f4b5
• Version Independent ID: ff9b78ce-a923-e763-08d5-c31cbb6a1f0e
• Content: Securing .NET Microservices and Web Applications
• Content Source: docs/architecture/microservices/secure-net-microservices-web-applications/index.md
• Product: dotnet-architecture
• Technology: microservices
• GitHub Login: @mjrousos
• Microsoft Alias: nanil

[tdykstra]

@mjrousos Can you help with this question?

[shoter]

It's not a question per se but rather a call to improve the documentation. Resolving question is not helpful compared to improving documentation on how to set authentication properly.

Thing that did not work for me with that example: I need to change default challenge schema to:

                options.DefaultChallengeScheme =
                   OpenIdConnectDefaults.AuthenticationScheme;

It's a pity schemes differences were not addressed here especially when there is openId default auth schema.

It would be great to have working example for example with docker compose.