Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage 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 Functionality already exists
Created by Guest
Created on Apr 12, 2023

modify behavior of ldap authentication cache expiration

Currently ldap authentication cache expiration timeouts can be set via commandline:
e.g.:
chldap -authcacheminutes 60
would set the authentication cache to be refreshed every hour.

This is a fixed timer that starts to count when user logs in and would cause a refresh of authentication cache after exact one hour.

We would like to change the behavior of this timeout value so that it is started after last active click in GUI or command line action.

Reason for this is that we use a LDAP server with OTP token / password authentication and the authentication cache will always return false in case of re-check.

Current solution is to set the authentication cache to a very high value in order to not being logged out every short period of time. Changing the behavior of cache timeout would make it more secure as we could use a very short authentication cache timeout after inactivity, easy comparable to MS Windows screensaver.

Idea priority Medium
  • Admin
    Philip Clark
    Reply
    |
    Jun 8, 2023

    Thank you for submitting this Idea. Your comments and feedback are important to us. We are currently evaluating your request.

    There are existing GUI and CLI timeouts that allow you to do this:
    https://www.ibm.com/docs/en/flashsystem-7x00/8.5.x?topic=csc-chsecurity-2

    It sounds like you are using the cache timer as an inactivity timer. It may be better option to disable the cache and use the timeout values.

    I will ask the team to reach out via email to discuss in more detail and ensure that we understand your requirements.

    We appreciate your input and hope that you will continue to submit enhancement requests.


    Thanks,
    FlashSystem Team

    philipclark@ibm.com