Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Why does our internal server address appear when users authenticate against our SSO?

Written By

Nathan Roberts

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • When a user authenticates against an SSO they are redirected to the server they were logging into. As part of this both the SSO address and the server address appear in the URL for a brief time. This occurs despite there being a web server/load balancer/proxy in front of the Liferay DXP bundle.
  • Example using two Liferay DXP bundles hosted locally with a user authenticating via SAML: 
    http://localhost:8080/c/portal/saml/auth_redirect?redirect=http%3A%2F%2Flocalhost%3A8080%2F

Environment

  • Liferay DXP 7.0
  • Liferay DXP 7.1
  • Use  of Single Sign On authentication (via SAML, or LDAP, or CA, or other supported SSO)

Resolution

  • This is the expected behavior as the user is being redirected.
  • Masking or hiding the internal server address could be configured via the web server/load balancer/proxy that is being used in front of the Liferay DXP bundle(s). Unfortunately Liferay Support is limited in the assistance we can provide for this process.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?