Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Categories On-Prem
Created by Guest
Created on Oct 16, 2026

Implement proper SAML Single Logout (SLO) for the ActiveTransfer Web Client so that users are fully signed out from the Identity Provider upon logout.

Currently, when a user authenticated via SAML SSO logs out of the ActiveTransfer Web Client, only the local MFT session is terminated. The Identity Provider session (e.g. Keycloak, ADFS) remains active. As a result, clicking "Login again with Single Sign On" immediately re-authenticates the user without prompting for credentials — effectively making logout a no-op from a security perspective.

The SAML 2.0 standard defines a Single Logout (SLO) profile specifically to address this: upon logout, the Service Provider initiates a signed LogoutRequest to the IdP, which in turn invalidates the IdP session and returns a LogoutResponse. The necessary libraries (Spring Security SAML) are already part of the product stack and include a SingleLogoutProfile implementation. What is missing is the integration of this profile into the logout flow of the Web Client.

The fix would require the logout handler to generate a SAML SLO redirect to the IdP instead of simply closing the local session, and a corresponding endpoint to process the LogoutResponse returned by the IdP.

Idea priority Medium