Failing VA when the Tableau Server uses SSL for the repository

Version 5

    I've been testing the TS repository SSL setting and it gave me some issues with VA 2.1.1.  Here's what I discovered...

     

    Body of email from VizAlerts:

    HTTPError generating trusted ticket: Not Found Request details: Server: tableau-test.corpintra.com, Site: , Username: terkson, Url: http://tableau-test.corpintra.com/trusted, Postdata: username=americas.corpdir.com%5Cterkson.

     

    vizalerts.log_date.log entry:

    MainThread - 2019-11-27 10:36:02 - [INFO] - LoggerQuickSetup - Logging initialized, writing to .\logs\vizalerts.log_2019-11-27.log

    MainThread - 2019-11-27 10:36:02 - [INFO] - main - VizAlerts v2.1.1 is starting

    MainThread - 2019-11-27 10:36:02 - [DEBUG] - trusted_ticket_test - testing trusted ticket: tableau-test.corpintra.com, terkson, americas.corpdir.com, None

    MainThread - 2019-11-27 10:36:02 - [DEBUG] - get_trusted_ticket - Generating trusted ticket. Request details: Server: tableau-test.corpintra.com, Site: , Username: terkson, Url: http://tableau-test.corpintra.com/trusted, Postdata: username=americas.corpdir.com%5Cterkson.

    MainThread - 2019-11-27 10:36:02 - [DEBUG] - get_trusted_ticket - NOT using SSL and NOT verifying cert

    MainThread - 2019-11-27 10:36:02 - [ERROR] - get_trusted_ticket - HTTPError generating trusted ticket: Not Found  Request details: Server: tableau-test.corpintra.com, Site: , Username: terkson, Url: http://tableau-test.corpintra.com/trusted, Postdata: username=americas.corpdir.com%5Cterkson.

    MainThread - 2019-11-27 10:36:02 - [ERROR] - trusted_ticket_test - HTTPError generating trusted ticket: Not Found  Request details: Server: tableau-test.corpintra.com, Site: , Username: terkson, Url: http://tableau-test.corpintra.com/trusted, Postdata: username=americas.corpdir.com%5Cterkson.

    MainThread - 2019-11-27 10:36:02 - [INFO] - send_email - sending email: mail.us164.corpintra.com,dw_164_tableau-support@my-company.com,toby.erkson@my-company.com, nishant.saxena@my-company.com,None,None,ALERT: VizAlerts failed to execute properly (NEW PROD),None

    MainThread - 2019-11-27 10:36:02 - [DEBUG] - send_email - email body: HTTPError generating trusted ticket: Not Found  Request details: Server: tableau-test.corpintra.com, Site: , Username: terkson, Url: http://tableau-test.corpintra.com/trusted, Postdata: username=americas.corpdir.com%5Cterkson.

    MainThread - 2019-11-27 10:36:02 - [DEBUG] - send_email - TO ADDRESS: toby.erkson@my-company.com, nishant.saxena@my-company.com

    MainThread - 2019-11-27 10:36:02 - [DEBUG] - send_email - CC ADDRESS: None

    MainThread - 2019-11-27 10:36:02 - [DEBUG] - send_email - BCC ADDRESS: None

    MainThread - 2019-11-27 10:36:02 - [ERROR] - <module> - An unhandled exception occurred: Traceback (most recent call last):

      File "vizalerts.py", line 488, in <module>

      File "vizalerts.py", line 129, in main

      File "vizalerts.py", line 205, in trusted_ticket_test

      File "vizalerts.py", line 474, in quit_script

    SystemExit: 1

     

    Fix:

    Under # Security settings in the vizalerts.yaml configuration file set the server.ssl to true.

     

    Why?

    This is due to using an address that uses SSL to route traffic to the primary TS and thus using that address in the vizalerts.yaml file in the server setting:

     

    In my case, we use a VIP (Virtual IP) URL that employs SSL, however, our TS itself does not use SSL.

    If I had used the server name (prodhostw018...) then the server.ssl would remain as false.

     

    Note that the server's Repository SSL being turned on for "Optional for user connections" setting as shown below does not matter: