RestMon Loses SAAS Communication
search cancel

RestMon Loses SAAS Communication

book

Article ID: 246197

calendar_today

Updated On:

Products

DX Operational Intelligence

Issue/Introduction

If changing the ‘saas.enabled’ parameter on Restmon application.properties to ‘true’, here is what happened:

 

  • few swagger methods simply disappear from the UI:
    • GET /v1/oiconnection
    • PUT /v1/oiconnection
    • DELETE /v1/oiconnection/{oiconnectionName}

 

  • And if invoking for ext GET /v1/profiles, it just rejects the token and throws an error on both SwaggerUI and logs:

{

  "Error": "Authentication failed:Token is empty"

}

 

[https-jsse-nio-8943-exec-3] DEBUG TenantAuthentication:91 - Cookies Received with Name : JSESSIONID and Value: 5E045F805E39826F1CD0D2EA2C768DB7

[https-jsse-nio-8943-exec-3] INFO  TenantAuthentication:122 - Authentication failed. Cookie object is null

[https-jsse-nio-8943-exec-3] ERROR Profiles:269 - Error in getting profiles list

com.ca.ce.restmon.app.security.InvalidSessionException: Authentication failed:Token is empty

 

Even though the token exists and it is valid on .json file. And I’ve tried to recreate the token several times, it leads to the same.

Environment

Release : 21.3

Component : CA DOI Foundations - DEFAULT

Cause

Saas.enabled is not applicable for the onprem RESTMon setups. The OI settings has to be updated corresponding to the SaaS setup or the on-prem OI. This flag should be left with default value of disabled in all deployments.

Resolution

On an On-Prem environment, this flag should be left with default value of disabled in all deployments.