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 Future consideration
Workspace DataPower Gateway
Created by Guest
Created on May 22, 2023

Support caching for the AAA post processing step

The current implementation of the AAA policy supports caching for the Authentication (AU) and the Authorization (AZ) step but it doesn't support caching for the Post Processing (PP) step.

The caching of the PP step would be helpful for all cases where the AAA policy has to generated tokens. Currently the PP step will generate a new token for each transaction even if the original user still has an acitve entry in the AU and/or AZ cache. This leads to the situation that the following processor, usually the backend, can not cache the token as it's always a new one.

A configurable caching of the PP step which is tied to the AU/AZ cache would simplify and improve the overall processing, especially in the OAuth/OIDC and SAML world.

Idea priority Medium