cf-auth-proxy slow to authorize when user has access to a large number of apps
Closed this issue · 3 comments
pianohacker commented
For users that are not admins (do not have logs.admin or doppler.firehose scopes in UAA), but have access to a large number of apps (hundreds or thousands), the cf-auth-proxy can take as long as 60 seconds to determine what apps the user has access to.
This information is cached, but due to load balancing, the benefit of that cache for latency purposes is reduced.
cf-gitbot commented
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
jaironpm commented
is there an update on this please?
pianohacker commented