Integration
Hide about this portal


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.


Add a new idea Subscribe
Status Under review
Workspace Aspera Ideas
Created by Guest
Created on Apr 16, 2024

RELATED IDEAS

[Orchestrator] Respect permissions for API

See this idea on ideas.ibm.com

Appears that to be able to run next api calls the user needs to have Aspera:Orchestrator:Monitor permissions:


${orcUrl}/aspera/orchestrator/api/work_orders_list/${workflow_id}?format=json&status=${status}&max_results=${maxResults}&from_date=${fromDate}&to_date=${endDate}

${orcUrl}/aspera/orchestrator/work_orders/initiate/fb5a2fc0-46b5-0139-a8a9-02172907afc6.json?

${orcUrl}/aspera/orchestrator/api/work_order_status/${id}?format=json

 

The only one that doesnt need monitor permission is the API call:

${orcUrl}/aspera/orchestrator/api/work_step_status/work_order?format=json&work_order_id=${workOrderId}&step_name=status_consumer

 

requiring system monitoring access to run or view a workflow allows users to also access workflow and system monitoring when i do not want them to. It also enables them to affect the monitoring by turning it off. This is dangerous.  In my opinion, having permissions to VIEW and RUN specific workflows is all they should need to use the APIs that view or run specific workflows.

 

Idea priority Urgent

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.