Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Under review
Categories Integration
Created by Guest
Created on Apr 6, 2026

Add the option to use basic authentication in the OAuth 2.0 authentication token request

According to RFC 6749, clients with a client password may use the HTTP Basic authentication to authenticate with the authorization server. (https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1).

However, in the current version of Maximo Manage, OAUTHCLIENT can only send the client ID and client secret in the HTTP body during the token request. If the authentication service only handles this information inside the basic authentication header, a costly customization is required.

The request is to add this option to avoid any customization.

Idea priority Low
Needed By Yesterday (Let's go already!)
  • ADMIN RESPONSE
    Sep 24, 2026

    Hi,

    Thank you for taking the time to provide your ideas to IBM. This Idea is now Under Review. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas. Thank you again for your feedback.

  • Guest
    Sep 16, 2026

    We have an integration via REST API with an external system. We follow the configuration steps detailed in Configuring OAuth access but when we call the service we receive an authentication error because the service expect to receive the credential in "Authorization: Basic" header of the request. With current Maximo implementation, clientId and clientSecret are passed in message body during oauth/token request.

  • Guest
    Sep 15, 2026

    I'm not sure I fully understand this requirement, so I think we need a bit more information about the flow.

    When you mention the token request, do you mean you have a MAS integration registered as an OIDC client?

    Is this request related to the MAS OIDC support introduced in 9.1, with MAS acting as the OIDC client?