You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Authorization call between internal services will request IDS server to get token each time. Is it necessary to cache client or user's access_token according to grant_type and ExpiresIn after the first request is successful to reduce the pressure on IDS server for each call? Of course, the token needs to be encrypted again
This is often the case when a domain event requires the invocation of a remote service, and events are generally stateless
thrownewAbpException($"Could not get token from the OpenId Connect server! ErrorType: {tokenResponse.ErrorType}. Error: {tokenResponse.Error}. ErrorDescription: {tokenResponse.ErrorDescription}. HttpStatusCode: {tokenResponse.HttpStatusCode}");
Authorization call between internal services will request IDS server to get token each time. Is it necessary to cache client or user's access_token according to grant_type and ExpiresIn after the first request is successful to reduce the pressure on IDS server for each call? Of course, the token needs to be encrypted again
This is often the case when a domain event requires the invocation of a remote service, and events are generally stateless
abp/framework/src/Volo.Abp.IdentityModel/Volo/Abp/IdentityModel/IdentityModelAuthenticationService.cs
Lines 71 to 94 in cf39e47
The text was updated successfully, but these errors were encountered: