Configuring Restriction to IP Address based on Authentication
About this task
You must have the Manage Security Configuration functional privilege to configure this restriction.
Configure the restriction to client IP address based on authentication failure in webMethods API Gateway to prevent malicious attack. This attack occurs when a client floods a server with many requests in an attempt to interfere with server processing. This restriction prevents the malicious attack by blocking or denying the unauthenticated client from accessing the APIs, when webMethods API Gateway fails to authenticate the client. Using webMethods API Gateway, you can limit the number of times a client fails to authenticate the API in a specified time interval. The reason for authentication failure can be such as:
- when webMethods API Gateway fails to authenticate the client (or)
- when webMethods API Gateway fails to identify the client and its respective application.
- When authentication failure occurs, webMethods API Gateway sends the 401 or 403 error message to the client.
- When webMethods API Gateway detects that the failed authentication limit has been exceeded, it blocks or denies access to that client IP address. It then sends a 403 Forbidden error to the client.
- If an API uses the Identify and Access Application policy and the invocation fails due to non-preemptive authentication, webMethods API Gateway does not count this failure toward the failed authentication limit.
- When you use Load Balancer for configuring high availability between the webMethods API Gateway instances, webMethods API Gateway honors the X-Forwarded-For (XFF) header from the client. As the XFF header has the actual client IP address, webMethods API Gateway can block or deny the problematic client from accessing the protected API based on your configuration.

You can configure restriction to IP address based on authentication.