For the current understanding of IdentityServer4, I found that the basic interface permission configuration is more suitable for permission control projects with multiple WebApi However, the current project requirement is to authorize different interfaces in the same WebApi that can be automatically generated later. Can IdentityServer meet this requirement? If it can be done, is there a similar demo? Above I put a rough expected flow chart
To implement modern authorization I would recommend that you use the built in Policy-based authorization in ASP.NET Core.
This allows you to decouple the authorization rules from the actual API-controllers and action methods in your API, like this picture tries to show:
See this link for examples