Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Security
Created by Guest
Created on Oct 2, 2023

Refresh Token provided in HTTP Headers

  • Current situation: The OpenID Connect refresh token is sent as a GET parameter to the webservers of pem-pp and pem-pr applications so the refresh token is showed in the URL history of the browser/sniffer traffic:

Example:

GET
/rochesso/home?refreshToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJTcG9uc29ySUQiOiI3MDQxZmU
zMi02Y2MwLTQ5NDctODE4Yi1hMjc1MDkwZWU4NzYiLCJVc2VySUQiOiI2NjA0MGFlMC03OTA0LTQzNGQtOGJlNy03OTI
1YzZiYjc0ZjYiLCJGaXJzdE5hbWUiOiJiMmJwbnQwMSIsImlzcyI6IlBFTV9SRUZSRVNIX0lTU1VFUiIsIkxhc3ROYW1
lIjoidXNlcjAxIiwiZXhwIjoxNjgwNTc0MTkyLCJJc1Nwb25zb3IiOnRydWUsInBlbS1ocy1pZCI6InhXZnRoZngzTGF
STRICTLY CONFIDENTIAL, Project 88310, v1.0, Section 4 Manual Hacking New Components
80/153MZHI5UUF6SS05NmlfIiwiUGFydGljaXBhbnRSb2xlIjoiQURNSU4ifQ.0N1OtGETSwIIVoIsAvmql6LAzQrLhvQAlnkv
eeCO6SY HTTP/1.1
  • Suggested situation: The token should be transferred via HTTP HEADERS or POST method to avoid hijacking session.


What is your industry? Healthcare
How will this idea be used?

As Solution Architecture I want Tokens not to be transferred via GET method to avoid exposure of the token if someone has access to the HTTP request history in order to have sessions more secure.