ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Log Analytics Login URL config

book

Article ID: 198956

calendar_today

Updated On:

Products

CA App Experience Analytics

Issue/Introduction

 

With AXA Log Analytics (LA) 17.3.0 5 node cluster built with Nginx enabled to facilitate SSL and all is working fine,

A number of DNS names have been defined for the LA front end to use rather than the FQDN in the URL.

When configuring Nginx the files in the apache-tomee-plus-1.7.1/webapp/admin folder are edited with the new address.


When using the DNS entry the login page loads but the login fails.

Unable to find any advice on adding additional URLs to this file

Environment

Release : 17.3

Component : AXA LOG ANALYTICS

Resolution

 

There is strict matching of URLs in the product configuration for security reasons. This is done in the Apache TomEE configuration as well as the Postgres database that keeps information about the application.

Multiple values cannot be configured either in the files or in the database.

Additional Information

 

This section of the documentation shows the places where the configuration needs to be changed

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/app-experience-analytics/17-3/troubleshooting/troubleshooting-post-installation.html#concept.dita_5a249b66e8e6fe1252e71c24ad58704794e3c6c9_unabletologintoadminconsoleUnabletoLogintotheAdministrationConsoleorSendDatafromtheInstrumentedApplication

Nginx SSL configuration shows procedure to configure Nginx and confirm URL configuration. For LA-only deployment, Nginx can be used in this way.

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/agile-operations-analytics-base-platform/17-3/installing-17-3-0-and-17-3-1/single-node-installation/post-installation-tasks-single-node.html