Cloud Platform


This is an IBM Automation portal for Cloud Platform 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.


Add a new idea Subscribe
Status Under review
Workspace WebSphere Liberty
Created by Guest
Created on Dec 11, 2025

RELATED IDEAS

How can we configure Liberty so that only specific URL patterns use OIDC, and all others bypass OIDC and fall back to BasicAuth—even if the JWT contains the same issuer?

We are using a single z/OS Connect server instance. After applying the OIDC configuration on the server, we observed that requests whose URL patterns do not match the configured OIDC scopes — but still contain a JWT in any header — do not fall back to Basic Authentication. Even the exclude URL pattern does not work in this scenario.

Our requirement is that any request whose URL pattern does not match should fall back to Basic Authentication even if it contains JWT, as we use OAuth 2.0 with the client-credentials flow.

Currently, single sign-on with the OIDC server configuration works correctly. The issue occurs only when a header manipulation policy replaces the Authorization header, changing it from the actual Bearer token to a Basic token.

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.