org.jclouds.rackspace.cloudloadbalancers.v1.features.SSLTerminationApi Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of rackspace-cloudloadbalancers Show documentation
Cloud Load Balancers API for Rackspace
The newest version!
/*
 * Licensed to the Apache Software Foundation (ASF) under one or more
 * contributor license agreements.  See the NOTICE file distributed with
 * this work for additional information regarding copyright ownership.
 * The ASF licenses this file to You under the Apache License, Version 2.0
 * (the "License"); you may not use this file except in compliance with
 * the License.  You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License 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 org.jclouds.rackspace.cloudloadbalancers.v1.features;

import jakarta.inject.Named;
import jakarta.ws.rs.Consumes;
import jakarta.ws.rs.DELETE;
import jakarta.ws.rs.GET;
import jakarta.ws.rs.PUT;
import jakarta.ws.rs.Path;
import jakarta.ws.rs.core.MediaType;

import org.jclouds.Fallbacks.FalseOnNotFoundOr422;
import org.jclouds.Fallbacks.NullOnNotFoundOr404;
import org.jclouds.Fallbacks.VoidOnNotFoundOr404;
import org.jclouds.openstack.keystone.auth.filters.AuthenticateRequest;
import org.jclouds.rackspace.cloudloadbalancers.v1.domain.SSLTermination;
import org.jclouds.rest.annotations.Fallback;
import org.jclouds.rest.annotations.RequestFilters;
import org.jclouds.rest.annotations.SelectJson;
import org.jclouds.rest.annotations.WrapWith;

/**
 * The SSL Termination feature allows a load balancer user to terminate SSL traffic at the load balancer layer versus 
 * at the web server layer. A user may choose to configure SSL Termination using a key and an SSL certificate or an 
 * (Intermediate) SSL certificate.
 *  
 * When SSL Termination is configured on a load balancer, a secure shadow server is created that listens only for 
 * secure traffic on a user-specified port. This shadow server is only visible to and manageable by the system. 
 * Existing or updated attributes on a load balancer with SSL Termination will also apply to its shadow server. 
 * For example, if Connection Logging is enabled on an SSL load balancer, it will also be enabled on the shadow server 
 * and Cloud Files logs will contain log files for both.
 * 

 * Notes
 * 

 * SSL Termination may only be configured on load balancers with non-secure protocols. For example, SSL Termination 
 * can be applied to an HTTP load balancer, but not to an HTTPS load balancer.
 * SSL-terminated load balancers decrypt the traffic at the traffic manager and pass unencrypted traffic to the 
 * back-end node. Because of this, the customer's back-end nodes don't know what protocol the client requested. 
 * Therefore the X-Forwarded-Proto (XFP) header has been added for identifying the originating protocol of an HTTP 
 * request as "http" or "https" depending on what protocol the client requested.
 * Not every service will return certificates in the proper order. Please verify that your chain of certificates 
 * matches that of walking up the chain from the domain to the CA root.
 * 
 * 
 * Warning
 * 
 * If SSL is enabled on a load balancer that is configured with nodes that are NOT in the same datacenter, then 
 * decrypted traffic will be sent in clear text over the public internet to the external node(s) and will no longer 
 * be secure.
 * 
 */
@RequestFilters(AuthenticateRequest.class)
public interface SSLTerminationApi {
   /**
    * Create or update SSL termination.
    * 
    * The following attributes may be updated without overwriting a load balancer's existing SSL certificate and key 
    * specifications:
    * 
    * enabled
    * secureTrafficOnly
    * securePort
    * 
    * These configurable attributes must be provided (individually or grouped) in a request without specifying any 
    * certificate/key combination if a user does not want the system to overwrite the existing SSL certificate/key 
    * configuration.
    * 
    * If a user wants to replace the existing SSL configuration, a new certificate, privatekey, and securePort 
    * combination must be provided instead of, or in addition to, the optional/editable attributes.
    */
   @Named("ssltermination:create")
   @PUT
   @Consumes(MediaType.APPLICATION_JSON) 
   @Fallback(VoidOnNotFoundOr404.class)
   @Path("/ssltermination")
   void createOrUpdate(@WrapWith("sslTermination") SSLTermination sslTermination);

   /**
    * Get SSL termination info.
    */
   @Named("ssltermination:get")
   @GET
   @Consumes(MediaType.APPLICATION_JSON)
   @SelectJson("sslTermination")
   @Fallback(NullOnNotFoundOr404.class)
   @Path("/ssltermination")
   SSLTermination get();
   
   /**
    * Delete SSL termination.
    * 
    * @return true on a successful delete, false if the SSL termination was not found
    */
   @Named("ssltermination:delete")
   @DELETE
   @Fallback(FalseOnNotFoundOr422.class)
   @Path("/ssltermination")
   @Consumes("*/*")
   boolean delete();
}