UCSD and UCSM HTTPS integration Example ( selfsigned/expired/invalid certificates)

Version 2
    Task NameCert integration Example
    Description
    1. Cert integration Example
    Prerequisites
    1. Tested on 5.3.x
    CategoryWorkflow
    ComponentsvSphere 5.x
    User Inputs

    Instructions for Regular Workflow Use:

    1. Download the attached .ZIP file below to your computer. *Remember the location of the saved file on your computer.
    2. Unzip the file on your computer. Should end up with a .WFD file.
    3. Log in to UCS Director as a user that has "system-admin" privileges.
    4. Navigate to "Policies-->Orchestration" and click on "Import".
    5. Click "Browse" and navigate to the location on your computer where the .WFD file resides. Choose the .WFD file and click "Open".
    6. Click "Upload" and then "OK" once the file upload is completed. Then click "Next".
    7. Click the "Select" button next to "Import Workflows". Click the "Check All" button to check all checkboxes and then the "Select" button.
    8. Click "Submit".
    9. A new folder should appear in "Policies-->Orchestration" that contains the imported workflow. You will now need to update the included tasks with information about the specific environment.

     

     

     

    In case we have a server that presents invalid SSL certificate, and we need to invoke the server from UCSD, use the CloupiaScript attached to this workflow. This scenario occurs very often in DEV/TEST environments. The script will trust all certificates presented by any server irrespective of selfsigned/authoritysigned/expired/server-validity.

     

    (However, any PRODUCTION server should present valid certificates and the following code should not be used in Production)

     

    Custom Workflow Task: Get_UCSM_https_ServiceProfileBootOrder

    Workflow using this task : Get UCSM Boot Order (Custom Task HTTPS)