Activities of "KevinLG"

So if I understand correctly, to handle locally Roles and Permissions for external users (our SSO), we need a local authentication server, to handle our external provider (our SSO), and create users as "external user" in our system.

Or could I add a reference to AbpAccountPublicWebModule in the HttpApi tier, and handle it there ?

Hello, thank for your answer

Yes, we could, but we are in a tiered architecture and we surely don't want having a direct dependency from our Web tier, to the database.

What we are looking for here is more architecture guideline. How to have custom external authentication in a tiered architecture, without relying on a the XXX.IdentityServer site (which access directly to the database).

What we currently have :

• XXX.HttpApi : Our APIs, having a direct access to database;
• XXX.Web : Our back office website, accessing data only through HttpApi (via dynamic proxies)

Both authenticated with a custom external prodiver, implementing oidc:

• XXX.HttpApi : Use introspection to validate the accessToken passed.
• XXX.Web : Use AbpOpenIdConnect integration

What we would like, is populating own XXX user lists (ASP.NET Identity based), from external authentication, without breaking tiered-architecture