This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Enhancing Ocelot to Automatically Forward Claims from IdentityServer's Introspection Endpoint to Backend Services #2024
Labels
Authentication
Ocelot feature: Authentication
Authorization
Ocelot feature: Authorization
waiting
Waiting for answer to question or feedback from issue raiser
We expect Ocelot to forward the claims obtained from IdentityServer4's introspection endpoint to the backend services, enabling efficient authentication and authorization within our microservice architecture.
Currently, Ocelot does not forward the claims retrieved from the introspection endpoint to the backend services. This leads to inefficiencies, as each microservice must independently query IdentityServer4 for claims, resulting in unnecessary round trips.
To optimize our authentication and authorization process, we aim to enhance Ocelot's functionality. Specifically, we seek a feature that automatically passes the obtained claims from the introspection endpoint to the backend services, reducing reliance on IdentityServer and minimizing round trips.
Configure Ocelot as the API Gateway in a microservice architecture.
Integrate IdentityServer4 for authentication and authorization.
Ensure each microservice sends requests to IdentityServer4's introspection endpoint to retrieve claims.
Observe that Ocelot does not forward the obtained claims to the backend services.
Version: Ocelot 18.0
Platform: .NET 6
Subsystem: Authentication and Authorization
The text was updated successfully, but these errors were encountered: