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
Comment written by Gerald Maale on 29/05/2021 10:37:48
Hi, Don't you think using IMemoryCache stores the token in the entire server where notwithstanding who logs in, the token is not actually representing the new user logging in. You consider revising this.
Comment written by Alexandre on 22/08/2021 22:53:54
Good remark but in my sample the call to the API is made as a Service, not as a User: in that case caching the token for the whole server is what I want. But I agree with you,in other cases involving multiple users the implementation should be modified a bit.
Activity
TechWatching commentedon Oct 19, 2021
Comment written by Gerald Maale on 29/05/2021 10:37:48
Hi,
Don't you think using IMemoryCache stores the token in the entire server where notwithstanding who logs in, the token is not actually representing the new user logging in. You consider revising this.
TechWatching commentedon Oct 19, 2021
Comment written by Alex Pavlenko on 07/07/2021 02:46:29
If this is the inner service that should be used for entire application, why not?
TechWatching commentedon Oct 19, 2021
Comment written by Alexandre on 22/08/2021 22:53:54
Good remark but in my sample the call to the API is made as a Service, not as a User: in that case caching the token for the whole server is what I want. But I agree with you,in other cases involving multiple users the implementation should be modified a bit.
[-]Handle token retrieval while querying an API[/-][+]posts/delegating-handler[/+]