3153243 - How to control access to Cloud Integration iflow inbound endpoint (with Basic Authentication) individually in NEO?

There are multiple endpoints within one single iflow, or from different iflows deployed in Cloud Integration, NEO environment.
Secured connections with Basic Authentication following document Setting Up Inbound HTTP Connections (with Basic Authentication), Neo Environment
You notice users with role ESBMessaging.send can access all endpoints to send message. You want to know how to restrict specific user to be able to access specific endpoint only. Such as:

• User A only has access to endpoint A;
• User B only has access to endpoint B.

All images are taken from an internal demo system. Any resemblance to real data is a mere coincidence.

• Cloud Integration, NEO environment

401, 403, authorization, allow, limit, userrole, invoke endpoint, trigger message, custom role, customize role, restrict, control, minimize , KBA , LOD-HCI-PI-RT , Integration Runtime , How To