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 Under review
Workspace API Connect
Created by Guest
Created on Jun 12, 2025

Drupal hooks - ability to distinguish source of action

We are currently using few Drupal hooks to extend our Developer Portal behavior to push application data to external system in some specific situations using:
hook_apic_app_update, hook_apic_app_create, hook_apic_app_pre_delete, hook_apic_app_post_delete
https://www.ibm.com/docs/en/api-connect/10.0.8_lts?topic=extend-custom-module-development-using-hooks

We used to have similar solution in APIC v5 (currently we are on APIC 10.0.8.1) where the integration worked +/- fine but starting with APIC v10 we discovered that e.g. hook_apic_app_update is no longer triggered only on user action in Developer Portal but also on internal system synchronization between API Manger and Developer Portal which is unwanted situation. We applied workaround to check Drupal currentUser() inside the hook and discard all situation when user is not a real user.

Unfortunately our investigation shows that after migration from APIC v5 to v10 the behavior of those hooks changed so they are in fact triggered now in at least 3 situations: 
- in case user performs action in Developer Portal (Drupal currentUser() shows REAL user triggered action)
- in case user performs action in API Manager (Drupal currentUser() shows SYSTEM user triggered action)
- in case internal system synchronization happens (Drupal currentUser() shows SYSTEM user triggered action)

It means that if we are "protecting" our code in the hook to not being invoked on SYSTEM user action we are also blocking all incoming manual user actions from API Manager. 
We are looking for a solution to distinguish if the hook has been triggered by:
1. Real user action in Developer Portal
2. Real user action in API Manager UI 
3. Internal data synchronization processes

Possible solutions could be something like specific username or new Drupal context variable.

Idea priority High