-
-
Notifications
You must be signed in to change notification settings - Fork 763
Best practise for endpoint disabling? #2796
Comments
There's an Endpoints option: https://identityserver.github.io/Documentation/docsv2/configuration/identityServerOptions.html that you can use to disable individual endpoints. |
@brockallen I already found that; I know how to disable endpoints, I'm asking for opinions on whether I should! |
So the answer is yes -- that's why we have those settings. If you're not using them, then don't expose them. |
Is there definitive documentation as to which endpoints are required for each of the flows? I had a look but couldn't find anything exhaustive, and the Endpoints documentation listed here doesn't seem to cover every endpoint available to enable/disable? |
We don't, but that's a good idea for documentation. IdentityServer/Documentation#198 |
OK, I guess I'll play around and work out which endpoints I can ditch one by one without breaking anything! Thanks @brockallen |
Yep, that's a reasonable way to start :) |
For reference in case anyone is interested, the following endpoint config seems to work for us using ImplicitFlow:
|
Does anyone have any guidance on best practise re: disabling endpoints? Our implementation is only using the Implicit Flow type which I believe means we can disable some of the endpoints (e.g. Token & TokenRevocation) but I'm not sure if I'm being overzealous. Is it insecure to leave the endpoints available even if we aren't using them?
The text was updated successfully, but these errors were encountered: