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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Thank you for the additional clarification. We understand the security concern regarding the visibility of the ArcGIS access token through browser developer tools.
In the current browser-based architecture, the token is used by the client to authenticate requests directly to the secured ArcGIS service. Because the browser must have access to the token in order to make those requests, masking or additionally encrypting the value on the client side would not prevent a user with access to the browser's network inspection tools from observing the authentication information used in the actual request.
The communication itself is protected through HTTPS, which protects the token while it is in transit. Completely preventing the ArcGIS token from reaching the browser would require a different architectural approach in which the requests are mediated server-side rather than sent directly from the browser to ArcGIS.
We will continue to evaluate improvements to authentication and token management, particularly around token lifetime, reuse, and limiting unnecessary exposure, but masking the token in browser network traffic would not by itself address the underlying concern.