/* * 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.apigateway.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.protocol.StructuredPojo; import com.amazonaws.protocol.ProtocolMarshaller; /** *

* Specifies the TLS configuration for an integration. *

*/ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class TlsConfig implements Serializable, Cloneable, StructuredPojo { /** *

* Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is * issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that * are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway * still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, * and presence of a root certificate authority. Supported only for HTTP and HTTP_PROXY * integrations. *

* *

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public HTTPS * endpoints. If you enable insecureSkipVerification, you increase the risk of man-in-the-middle * attacks. *

*
*/ private Boolean insecureSkipVerification; /** *

* Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is * issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that * are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway * still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, * and presence of a root certificate authority. Supported only for HTTP and HTTP_PROXY * integrations. *

* *

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public HTTPS * endpoints. If you enable insecureSkipVerification, you increase the risk of man-in-the-middle * attacks. *

*
* * @param insecureSkipVerification * Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint * is issued by a supported certificate authority. This isn’t recommended, but it enables you to use * certificates that are signed by private certificate authorities, or certificates that are self-signed. If * enabled, API Gateway still performs basic certificate validation, which includes checking the * certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for * HTTP and HTTP_PROXY integrations.

*

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public * HTTPS endpoints. If you enable insecureSkipVerification, you increase the risk of * man-in-the-middle attacks. *

*/ public void setInsecureSkipVerification(Boolean insecureSkipVerification) { this.insecureSkipVerification = insecureSkipVerification; } /** *

* Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is * issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that * are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway * still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, * and presence of a root certificate authority. Supported only for HTTP and HTTP_PROXY * integrations. *

* *

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public HTTPS * endpoints. If you enable insecureSkipVerification, you increase the risk of man-in-the-middle * attacks. *

*
* * @return Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint * is issued by a supported certificate authority. This isn’t recommended, but it enables you to use * certificates that are signed by private certificate authorities, or certificates that are self-signed. If * enabled, API Gateway still performs basic certificate validation, which includes checking the * certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for * HTTP and HTTP_PROXY integrations.

*

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public * HTTPS endpoints. If you enable insecureSkipVerification, you increase the risk of * man-in-the-middle attacks. *

*/ public Boolean getInsecureSkipVerification() { return this.insecureSkipVerification; } /** *

* Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is * issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that * are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway * still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, * and presence of a root certificate authority. Supported only for HTTP and HTTP_PROXY * integrations. *

* *

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public HTTPS * endpoints. If you enable insecureSkipVerification, you increase the risk of man-in-the-middle * attacks. *

*
* * @param insecureSkipVerification * Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint * is issued by a supported certificate authority. This isn’t recommended, but it enables you to use * certificates that are signed by private certificate authorities, or certificates that are self-signed. If * enabled, API Gateway still performs basic certificate validation, which includes checking the * certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for * HTTP and HTTP_PROXY integrations.

*

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public * HTTPS endpoints. If you enable insecureSkipVerification, you increase the risk of * man-in-the-middle attacks. *

* @return Returns a reference to this object so that method calls can be chained together. */ public TlsConfig withInsecureSkipVerification(Boolean insecureSkipVerification) { setInsecureSkipVerification(insecureSkipVerification); return this; } /** *

* Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is * issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that * are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway * still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, * and presence of a root certificate authority. Supported only for HTTP and HTTP_PROXY * integrations. *

* *

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public HTTPS * endpoints. If you enable insecureSkipVerification, you increase the risk of man-in-the-middle * attacks. *

*
* * @return Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint * is issued by a supported certificate authority. This isn’t recommended, but it enables you to use * certificates that are signed by private certificate authorities, or certificates that are self-signed. If * enabled, API Gateway still performs basic certificate validation, which includes checking the * certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for * HTTP and HTTP_PROXY integrations.

*

* Enabling insecureSkipVerification isn't recommended, especially for integrations with public * HTTPS endpoints. If you enable insecureSkipVerification, you increase the risk of * man-in-the-middle attacks. *

*/ public Boolean isInsecureSkipVerification() { return this.insecureSkipVerification; } /** * Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be * redacted from this string using a placeholder value. * * @return A string representation of this object. * * @see java.lang.Object#toString() */ @Override public String toString() { StringBuilder sb = new StringBuilder(); sb.append("{"); if (getInsecureSkipVerification() != null) sb.append("InsecureSkipVerification: ").append(getInsecureSkipVerification()); sb.append("}"); return sb.toString(); } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (obj instanceof TlsConfig == false) return false; TlsConfig other = (TlsConfig) obj; if (other.getInsecureSkipVerification() == null ^ this.getInsecureSkipVerification() == null) return false; if (other.getInsecureSkipVerification() != null && other.getInsecureSkipVerification().equals(this.getInsecureSkipVerification()) == false) return false; return true; } @Override public int hashCode() { final int prime = 31; int hashCode = 1; hashCode = prime * hashCode + ((getInsecureSkipVerification() == null) ? 0 : getInsecureSkipVerification().hashCode()); return hashCode; } @Override public TlsConfig clone() { try { return (TlsConfig) super.clone(); } catch (CloneNotSupportedException e) { throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e); } } @com.amazonaws.annotation.SdkInternalApi @Override public void marshall(ProtocolMarshaller protocolMarshaller) { com.amazonaws.services.apigateway.model.transform.TlsConfigMarshaller.getInstance().marshall(this, protocolMarshaller); } }