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
Workspace DataPower Gateway
Created by Guest
Created on Jun 9, 2026

Add clock skew to JWT validation

Currently the validate operation of the Decoder.addOperation() function of the JWT module (jwt module - IBM Documentation) does not use or support a clock skew. This will cause sporadic false positive validation failures, which are not acceptable.

Thus we curently cannot use this built-in validation functionality. Instead we must code the validation logic for 'nbf' and 'exp' claims by hand.

This proposal is to add support for a clock skew parameter, which will consider the clock skew when validating the 'nbf' and 'exp' claims.

This blog describes why clock skew is important in JWT validation, and also states that it is industry standard to include a 5 second clock skew: JWT clock skew: why your tokens expire before they should — Bastionary Blog

Idea priority Medium