Identityserver4: Discuss throttling
- entire server?
- particular endpoint?
- status codes?
leastprivilege
All 5 comments
Should this be part of IdentityServer4? seems like something that would be best tackled by just using another middleware which has the configurability to throttle endpoint(s)
Lutando
on 19 Sep 2016
I agree - that's why this issue is called "discuss" ;)
leastprivilege
on 19 Sep 2016
I only think there are 2 places that might need this -- userinfo and introspection, and I think these possible caching considered here: https://github.com/IdentityServer/IdentityServer4/issues/253#issuecomment-252445187 will be sufficient in addressing any flooding issues.
brockallen
on 9 Oct 2016
The kind of throttling we were discussing would need to be done more inside IdSvr with more intelligence, so this issue will be the main one to satisfy this: https://github.com/IdentityServer/IdentityServer4/issues/253
brockallen
on 9 Oct 2016
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
![lock[bot] picture](https://avatars1.githubusercontent.com/in/6672?v=4&s=40)
lock[bot]
on 15 Jan 2020
Related issues
klioqc
路
3Comments
nukec
路
3Comments
Aravind1729
路
3Comments
garymacpherson
路
3Comments
mackie1001
路
3Comments
Most helpful comment
Should this be part of IdentityServer4? seems like something that would be best tackled by just using another middleware which has the configurability to throttle endpoint(s)