/*
 * Copyright 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.
 */

/*
 * Do not modify this file. This file is generated from the wafv2-2019-07-29.normal.json service model.
 */
using System;
using System.Collections.Generic;
using System.Xml.Serialization;
using System.Text;
using System.IO;
using System.Net;

using Amazon.Runtime;
using Amazon.Runtime.Internal;

namespace Amazon.WAFV2.Model
{
    /// <summary>
    /// The criteria for inspecting account creation requests, used by the ACFP rule group
    /// to validate and track account creation attempts. 
    /// 
    ///  
    /// <para>
    /// This is part of the <code>AWSManagedRulesACFPRuleSet</code> configuration in <code>ManagedRuleGroupConfig</code>.
    /// </para>
    ///  
    /// <para>
    /// In these settings, you specify how your application accepts account creation attempts
    /// by providing the request payload type and the names of the fields within the request
    /// body where the username, password, email, and primary address and phone number fields
    /// are provided. 
    /// </para>
    /// </summary>
    public partial class RequestInspectionACFP
    {
        private List<AddressField> _addressFields = new List<AddressField>();
        private EmailField _emailField;
        private PasswordField _passwordField;
        private PayloadType _payloadType;
        private List<PhoneNumberField> _phoneNumberFields = new List<PhoneNumberField>();
        private UsernameField _usernameField;

        /// <summary>
        /// Gets and sets the property AddressFields. 
        /// <para>
        /// The names of the fields in the request payload that contain your customer's primary
        /// physical address. 
        /// </para>
        ///  
        /// <para>
        /// Order the address fields in the array exactly as they are ordered in the request payload.
        /// 
        /// </para>
        ///  
        /// <para>
        /// How you specify the address fields depends on the request inspection payload type.
        /// </para>
        ///  <ul> <li> 
        /// <para>
        /// For JSON payloads, specify the field identifiers in JSON pointer syntax. For information
        /// about the JSON Pointer syntax, see the Internet Engineering Task Force (IETF) documentation
        /// <a href="https://tools.ietf.org/html/rfc6901">JavaScript Object Notation (JSON) Pointer</a>.
        /// 
        /// </para>
        ///  
        /// <para>
        /// For example, for the JSON payload <code>{ "form": { "primaryaddressline1": "THE_ADDRESS1",
        /// "primaryaddressline2": "THE_ADDRESS2", "primaryaddressline3": "THE_ADDRESS3" } }</code>,
        /// the address field idenfiers are <code>/form/primaryaddressline1</code>, <code>/form/primaryaddressline2</code>,
        /// and <code>/form/primaryaddressline3</code>.
        /// </para>
        ///  </li> <li> 
        /// <para>
        /// For form encoded payload types, use the HTML form names.
        /// </para>
        ///  
        /// <para>
        /// For example, for an HTML form with input elements named <code>primaryaddressline1</code>,
        /// <code>primaryaddressline2</code>, and <code>primaryaddressline3</code>, the address
        /// fields identifiers are <code>primaryaddressline1</code>, <code>primaryaddressline2</code>,
        /// and <code>primaryaddressline3</code>. 
        /// </para>
        ///  </li> </ul>
        /// </summary>
        public List<AddressField> AddressFields
        {
            get { return this._addressFields; }
            set { this._addressFields = value; }
        }

        // Check to see if AddressFields property is set
        internal bool IsSetAddressFields()
        {
            return this._addressFields != null && this._addressFields.Count > 0; 
        }

        /// <summary>
        /// Gets and sets the property EmailField. 
        /// <para>
        /// The name of the field in the request payload that contains your customer's email.
        /// 
        /// </para>
        ///  
        /// <para>
        /// How you specify this depends on the request inspection payload type.
        /// </para>
        ///  <ul> <li> 
        /// <para>
        /// 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
        /// <a href="https://tools.ietf.org/html/rfc6901">JavaScript Object Notation (JSON) Pointer</a>.
        /// 
        /// </para>
        ///  
        /// <para>
        /// For example, for the JSON payload <code>{ "form": { "email": "THE_EMAIL" } }</code>,
        /// the email field specification is <code>/form/email</code>.
        /// </para>
        ///  </li> <li> 
        /// <para>
        /// For form encoded payload types, use the HTML form names.
        /// </para>
        ///  
        /// <para>
        /// For example, for an HTML form with the input element named <code>email1</code>, the
        /// email field specification is <code>email1</code>.
        /// </para>
        ///  </li> </ul>
        /// </summary>
        public EmailField EmailField
        {
            get { return this._emailField; }
            set { this._emailField = value; }
        }

        // Check to see if EmailField property is set
        internal bool IsSetEmailField()
        {
            return this._emailField != null;
        }

        /// <summary>
        /// Gets and sets the property PasswordField. 
        /// <para>
        /// The name of the field in the request payload that contains your customer's password.
        /// 
        /// </para>
        ///  
        /// <para>
        /// How you specify this depends on the request inspection payload type.
        /// </para>
        ///  <ul> <li> 
        /// <para>
        /// 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
        /// <a href="https://tools.ietf.org/html/rfc6901">JavaScript Object Notation (JSON) Pointer</a>.
        /// 
        /// </para>
        ///  
        /// <para>
        /// For example, for the JSON payload <code>{ "form": { "password": "THE_PASSWORD" } }</code>,
        /// the password field specification is <code>/form/password</code>.
        /// </para>
        ///  </li> <li> 
        /// <para>
        /// For form encoded payload types, use the HTML form names.
        /// </para>
        ///  
        /// <para>
        /// For example, for an HTML form with the input element named <code>password1</code>,
        /// the password field specification is <code>password1</code>.
        /// </para>
        ///  </li> </ul>
        /// </summary>
        public PasswordField PasswordField
        {
            get { return this._passwordField; }
            set { this._passwordField = value; }
        }

        // Check to see if PasswordField property is set
        internal bool IsSetPasswordField()
        {
            return this._passwordField != null;
        }

        /// <summary>
        /// Gets and sets the property PayloadType. 
        /// <para>
        /// The payload type for your account creation endpoint, either JSON or form encoded.
        /// </para>
        /// </summary>
        [AWSProperty(Required=true)]
        public PayloadType PayloadType
        {
            get { return this._payloadType; }
            set { this._payloadType = value; }
        }

        // Check to see if PayloadType property is set
        internal bool IsSetPayloadType()
        {
            return this._payloadType != null;
        }

        /// <summary>
        /// Gets and sets the property PhoneNumberFields. 
        /// <para>
        /// The names of the fields in the request payload that contain your customer's primary
        /// phone number. 
        /// </para>
        ///  
        /// <para>
        /// Order the phone number fields in the array exactly as they are ordered in the request
        /// payload. 
        /// </para>
        ///  
        /// <para>
        /// How you specify the phone number fields depends on the request inspection payload
        /// type.
        /// </para>
        ///  <ul> <li> 
        /// <para>
        /// For JSON payloads, specify the field identifiers in JSON pointer syntax. For information
        /// about the JSON Pointer syntax, see the Internet Engineering Task Force (IETF) documentation
        /// <a href="https://tools.ietf.org/html/rfc6901">JavaScript Object Notation (JSON) Pointer</a>.
        /// 
        /// </para>
        ///  
        /// <para>
        /// For example, for the JSON payload <code>{ "form": { "primaryphoneline1": "THE_PHONE1",
        /// "primaryphoneline2": "THE_PHONE2", "primaryphoneline3": "THE_PHONE3" } }</code>, the
        /// phone number field identifiers are <code>/form/primaryphoneline1</code>, <code>/form/primaryphoneline2</code>,
        /// and <code>/form/primaryphoneline3</code>.
        /// </para>
        ///  </li> <li> 
        /// <para>
        /// For form encoded payload types, use the HTML form names.
        /// </para>
        ///  
        /// <para>
        /// For example, for an HTML form with input elements named <code>primaryphoneline1</code>,
        /// <code>primaryphoneline2</code>, and <code>primaryphoneline3</code>, the phone number
        /// field identifiers are <code>primaryphoneline1</code>, <code>primaryphoneline2</code>,
        /// and <code>primaryphoneline3</code>. 
        /// </para>
        ///  </li> </ul>
        /// </summary>
        public List<PhoneNumberField> PhoneNumberFields
        {
            get { return this._phoneNumberFields; }
            set { this._phoneNumberFields = value; }
        }

        // Check to see if PhoneNumberFields property is set
        internal bool IsSetPhoneNumberFields()
        {
            return this._phoneNumberFields != null && this._phoneNumberFields.Count > 0; 
        }

        /// <summary>
        /// Gets and sets the property UsernameField. 
        /// <para>
        /// The name of the field in the request payload that contains your customer's username.
        /// 
        /// </para>
        ///  
        /// <para>
        /// How you specify this depends on the request inspection payload type.
        /// </para>
        ///  <ul> <li> 
        /// <para>
        /// 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
        /// <a href="https://tools.ietf.org/html/rfc6901">JavaScript Object Notation (JSON) Pointer</a>.
        /// 
        /// </para>
        ///  
        /// <para>
        /// For example, for the JSON payload <code>{ "form": { "username": "THE_USERNAME" } }</code>,
        /// the username field specification is <code>/form/username</code>. 
        /// </para>
        ///  </li> <li> 
        /// <para>
        /// For form encoded payload types, use the HTML form names.
        /// </para>
        ///  
        /// <para>
        /// For example, for an HTML form with the input element named <code>username1</code>,
        /// the username field specification is <code>username1</code> 
        /// </para>
        ///  </li> </ul>
        /// </summary>
        public UsernameField UsernameField
        {
            get { return this._usernameField; }
            set { this._usernameField = value; }
        }

        // Check to see if UsernameField property is set
        internal bool IsSetUsernameField()
        {
            return this._usernameField != null;
        }

    }
}