Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 (

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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Future consideration
Workspace Spectrum LSF
Components Scheduling
Created by Guest
Created on Jan 12, 2021

Add support to Kerberos ticket with new "renew-until" date for already submitted jobs

While using Kerberos ticket forwarding on a LSF cluster:

Currently TGT found on the submission host is copied to LSF cache and forwarded to the execution host at job submission; These tickets can be renewed automatically by LSF until the TGT "renew-util" date is reached.

This behaviour could introduce some issues for long-pending or long-running jobs on the clusters, especially in case the Kerberos tickets management system is a corporate service that could not be easily tuned for HPC purpose.

Proposal: Let LSF check for new TGT on the submission host for already submitted jobs - and update the cached TGT when applicable; Users and/or administrators could then manage to update TGT on the submission host, and LSF would propagate the new ticket to existing pending and running jobs.

This would be highly valuable to get rid of this "renew-until" limit.

  • Guest
    Mar 3, 2021

    Olivier, we've added this to our backlog, and will get to it when resource becomes available. Unfortunately I am not able to give a definitive time frame at the moment.

  • Guest
    Jan 18, 2021

    Thanks for your feedback;
    Yes I assume that even a partial solution would make sense;
    Updating the TGT for pending jobs would anyway reduce the risk to reach the renew-until limite date during computations.
    Best regards,
    O. Moritz

  • Guest
    Jan 17, 2021

    It is plausible to add an option to update the TGT for a pending job.
    However, once a job starts, there is no way in Kerberos to update the TGT.
    So we could only partially address the requirement in this RFE, is a partial solution useful?