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
Is your Enhancement request related to a problem? Please describe
It's not related to a problem, but i could totally implement this in some scenarios.
Describe the solution you'd like
Add two paramaters on endpoint to allow/deny ip(s).
This will only allow 2 ips to connect to this particular endpoint. New-UDEndpoint -Url "/test" -Method GET -Endpoint {} -Allow @('10.0.0.1','10.0.0.2')
This will deny these 2 ips to connect to this particular endpoint. New-UDEndpoint -Url "/test" -Method GET -Endpoint {} -Deny @('10.0.0.1','10.0.0.2')
I imagine that, if there is a combination of ip filtering and auth method, ip filtering would be checked first ..
The text was updated successfully, but these errors were encountered:
Is your Enhancement request related to a problem? Please describe
It's not related to a problem, but i could totally implement this in some scenarios.
Describe the solution you'd like
Add two paramaters on endpoint to allow/deny ip(s).
This will only allow 2 ips to connect to this particular endpoint.
New-UDEndpoint -Url "/test" -Method GET -Endpoint {} -Allow @('10.0.0.1','10.0.0.2')
This will deny these 2 ips to connect to this particular endpoint.
New-UDEndpoint -Url "/test" -Method GET -Endpoint {} -Deny @('10.0.0.1','10.0.0.2')
I imagine that, if there is a combination of ip filtering and auth method, ip filtering would be checked first ..
The text was updated successfully, but these errors were encountered: