Unable to login to Portal
search cancel

Unable to login to Portal

book

Article ID: 447590

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

You are unable to log in to the DX NetOps Portal after a successful installation. While the login page opens correctly, entering your credentials leads to a redirect that fails with an ERR_EMPTY_RESPONSE or a blank page.

Symptoms

  • The browser redirects to http://####:8381/sso/sign-in-process.jsp and hangs.
  • Browser developer tools show a "Provisional headers are shown" warning.
  • Required request headers, such as Content-Length, are missing from the login submission.
  • The SSOService.log shows errors: Failed to get txtSsoProductCode parameter: 400: Unable to parse form content.
  • A local POST request using curl from the portal server succeeds, indicating the SSO service is functional locally:
    • curl -v -X POST http://localhost:8381/sso/sign-in-process.jsp \
      -H "Content-Type: application/x-www-form-urlencoded" \
      --data "txtSsoProductCode=pc&txtSsoRedirectUrl=http://####:8181/pc/desktop/page&txtUsername=####&txtPassword=####"

    • The request returns a HTTP/1.1 302 Found with the correct Location redirect.

Environment

All supported NetOps Performance Management versions

Cause

A configured network proxy on the jump server or client machine intercepts the SSO authentication traffic. The proxy interferes with the POST request to the SSO service, causing the loss of essential HTTP headers required for parsing the login product code.

Resolution

You must ensure that traffic to the NetOps Portal server bypasses any active proxies.

  1. Temporarily disable the proxy settings in your browser or system environment to verify the login succeeds.
  2. Configure a proxy bypass (Exception list) for the IP address or Hostname of the NetOps Portal server (e.g., ####).
  3. Confirm that the login now proceeds successfully through the SSO sign-in process.