DX Platform 20.2.1 - Unable to login, login is successful but it immediately logout

book

Article ID: 209838

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

This is an on premise new install of the DX Platform 20.2.1 release on k8s.

Login is successful, but it immediately logout

This issue is occurring right after the successful install.

Cause

Related to defect DE489145. At present, this fix is expected to go into on premise 21.3 release. We do not have any ETA for on premise 21.3 release.

 

CA_CLOUD_MANAGEMENT cookie is not getting created because of the invalid domain. We are setting cookie on the parent domain. In this case, it looks like the last two domain segment ( example: gov.XX) from the hostname (example: myhost.abcd.gov.XX). This (gov.XX) is not a valid domain name for cookie because gov is a top level domain.

You can check the CA_CLOUD_MANAGEMENT cookie in developer tools > Application as follows.

Example 1: multi level domain ".myhost.abcd.gov.XX" is considered as invalid.

Example 2: multi level domain ".dxstag.tmpstag.ti....com.tr"  is considered as invalid.

Environment

DX Platform 20.2.1 ONLY

DX Operational Intelligence 20.2.1
DX Application Performance Management 20.2.1
DX AXA 20.2.1

Resolution

Solution:

Attached manager-20.70.10.tar.gz HOTFIX image that can use for DX Platform 20.2.1 release.

The HOTFIX image should be loaded into local repository, pushed into registry and then turn deployment (apmservices/manager).

For installation Instructions how to deploy new manager-20.70.10.tar.gz see: DX Platform - How to apply a new hotfix image?

 

Workaround:

Customers could map their host name on another host name which has only one segment in the top domain name. Then customers can access DX Manager with this new mapped host name.

For example map myhost.abcd.gov.XX on myhost.io or something similar

 

Attachments

manager-20.70.10.tar_1629711593690.gz get_app