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 Future consideration
Workspace API Connect
Created by Guest
Created on Feb 20, 2020

Dashboard with registered users information in API Connect

Occasionally we have to reset our APIC Developer Portals.

The Team follow IBM’s advice regarding how to reset the Portals - it is just a way of resetting the Portal to the vanilla version. This is achieved without impacting Portal user accounts (set up in a separate Local User Registry) or existing API Subscriptions.

We discovered an issue which is that when a developer Portal is reset, we lose visibility of the Portal User’s details and their history (i.e. how long they have had a Portal Account).

The Portal user’s details are not carried through from the Local User Registry. Rather, they are recreated in the Portal Registry when the user next logs into the Portal.

IBM have advised this is as designed in the Portal.

They advised that API Manager is the system of record for API consumers. However the API Manager does not provide visibility of as much information, or the same level of information.
For example API Manager does not:
i. Provide details of all registered Portal accounts, it only displays details of Portal Users who are Dev Org Owners.
ii. Record when the user first created their Portal Account.

This means we do not have a reliable or complete view of who has created an account on our Portals if we reset them.

This is an issue for us.

We have implemented a quarterly Portal access review process but we do not have reliable information to base this access review on.
It also causes audit trail / non-repudiation issues for us. If we felt a Portal user acted inappropriately, and the portal was reset, unless they are the Dev Org Owner we cannot confirm they had a Portal account at the time of the inappropriate behaviour.

Idea priority Low