/* * Copyright 2018-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with * the License. A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions * and limitations under the License. */ package com.amazonaws.services.wafv2.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.protocol.StructuredPojo; import com.amazonaws.protocol.ProtocolMarshaller; /** *
* The criteria for inspecting login requests, used by the ATP rule group to validate credentials usage. *
*
* This is part of the AWSManagedRulesATPRuleSet
configuration in ManagedRuleGroupConfig
.
*
* In these settings, you specify how your application accepts login attempts by providing the request payload type and * the names of the fields within the request body where the username and password are provided. *
* * @see AWS API * Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class RequestInspection implements Serializable, Cloneable, StructuredPojo { /** ** The payload type for your login endpoint, either JSON or form encoded. *
*/ private String payloadType; /** ** The name of the field in the request payload that contains your customer's username. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "username": "THE_USERNAME" } }
, the username field
* specification is /form/username
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named username1
, the username field
* specification is username1
*
* The name of the field in the request payload that contains your customer's password. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "password": "THE_PASSWORD" } }
, the password field
* specification is /form/password
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named password1
, the password field
* specification is password1
.
*
* The payload type for your login endpoint, either JSON or form encoded. *
* * @param payloadType * The payload type for your login endpoint, either JSON or form encoded. * @see PayloadType */ public void setPayloadType(String payloadType) { this.payloadType = payloadType; } /** ** The payload type for your login endpoint, either JSON or form encoded. *
* * @return The payload type for your login endpoint, either JSON or form encoded. * @see PayloadType */ public String getPayloadType() { return this.payloadType; } /** ** The payload type for your login endpoint, either JSON or form encoded. *
* * @param payloadType * The payload type for your login endpoint, either JSON or form encoded. * @return Returns a reference to this object so that method calls can be chained together. * @see PayloadType */ public RequestInspection withPayloadType(String payloadType) { setPayloadType(payloadType); return this; } /** ** The payload type for your login endpoint, either JSON or form encoded. *
* * @param payloadType * The payload type for your login endpoint, either JSON or form encoded. * @return Returns a reference to this object so that method calls can be chained together. * @see PayloadType */ public RequestInspection withPayloadType(PayloadType payloadType) { this.payloadType = payloadType.toString(); return this; } /** ** The name of the field in the request payload that contains your customer's username. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "username": "THE_USERNAME" } }
, the username field
* specification is /form/username
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named username1
, the username field
* specification is username1
*
* How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer * syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "username": "THE_USERNAME" } }
, the username
* field specification is /form/username
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named username1
, the username field
* specification is username1
*
* The name of the field in the request payload that contains your customer's username. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "username": "THE_USERNAME" } }
, the username field
* specification is /form/username
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named username1
, the username field
* specification is username1
*
* How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer * syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "username": "THE_USERNAME" } }
, the username
* field specification is /form/username
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named username1
, the username field
* specification is username1
*
* The name of the field in the request payload that contains your customer's username. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "username": "THE_USERNAME" } }
, the username field
* specification is /form/username
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named username1
, the username field
* specification is username1
*
* How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer * syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "username": "THE_USERNAME" } }
, the username
* field specification is /form/username
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named username1
, the username field
* specification is username1
*
* The name of the field in the request payload that contains your customer's password. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "password": "THE_PASSWORD" } }
, the password field
* specification is /form/password
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named password1
, the password field
* specification is password1
.
*
* How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer * syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "password": "THE_PASSWORD" } }
, the password
* field specification is /form/password
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named password1
, the password field
* specification is password1
.
*
* The name of the field in the request payload that contains your customer's password. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "password": "THE_PASSWORD" } }
, the password field
* specification is /form/password
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named password1
, the password field
* specification is password1
.
*
* How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer * syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "password": "THE_PASSWORD" } }
, the password
* field specification is /form/password
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named password1
, the password field
* specification is password1
.
*
* The name of the field in the request payload that contains your customer's password. *
** How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer syntax, * see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "password": "THE_PASSWORD" } }
, the password field
* specification is /form/password
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named password1
, the password field
* specification is password1
.
*
* How you specify this depends on the request inspection payload type. *
** For JSON payloads, specify the field name in JSON pointer syntax. For information about the JSON Pointer * syntax, see the Internet Engineering Task Force (IETF) documentation JavaScript Object Notation (JSON) Pointer. *
*
* For example, for the JSON payload { "form": { "password": "THE_PASSWORD" } }
, the password
* field specification is /form/password
.
*
* For form encoded payload types, use the HTML form names. *
*
* For example, for an HTML form with the input element named password1
, the password field
* specification is password1
.
*