Legacy Knowledge Base
Published Jun. 30, 2025

Is Liferay's SAML Service Provider Logout URL required in the Identity Provider?

Written By

Madeleine Clay

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

  • Azure's SAML Identity Provider (IdP) marks the Service Provider's (SP) Logout URL as "optional"
  • However, when I remove Liferay's Logout URL from Azure's SAML configurations, Liferay users are not signed out completely from Liferay after signing out through Azure.
  • Is it necessary to include Liferay's Logout URL in the Identity Provider's settings?

Environment

  • DXP 7.4

Resolution

  • It is necessary to either include the Logout URL or reference Liferay's SP Metadata (which includes the Logout URL) in the IdP.
  • This is because the SP receives the IdP's logout request at the Logout URL to complete the logout process.

Additional Information

  • Logout Process:
    1. The SP initiates the logout by sending the LogoutRequest to the IdP. This doesn’t change the SP’s session state

    2. The IdP then checks the SessionIndex provided by the SP request and sends a LogoutRequest to every other SP that is participating in that SessionIndex.

    3. Finally, the IdP sends a LogoutRequest to the SP which initiated the request.

  • See SAML Authentication Process Overview: Service Provider Initiated SLO for more details.
Did this article resolve your issue ?

Legacy Knowledge Base