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 Functionality already exists
Workspace App Connect
Created by Guest
Created on Nov 13, 2024

Administration REST API : mqsichangefileauth

Would like to be able to change rights on integration servers using the Administration REST API in order to segregate rights between different roles (admin vs read only for example).

Idea priority Medium
  • Guest
    Reply
    |
    Nov 25, 2024

    I have a concern because I would like to have an REST administration API endpoint to give rights on Integration Server without touching the node.conf.yaml or running locally the mqsichangefileauth command.

  • Admin
    Ben Thompson
    Reply
    |
    Nov 25, 2024

    Thank you for taking the time to raise this idea. For node-owned integration servers, the node.conf.yaml file enables users to define both Intgeration Node level permissions and Integration Server specific level permissions. The extract below shows these settings. For each server, you can uncomment roles (named to your choosing) such as the example "viewRole" and "adminRole", and then when defining each web user, you can map them to one of these roles in order to assign them the privileges (such as read/write/execute etc) that you would like that group of users to have.


      Node:
    Permissions:
    # Set Admin Security Authorization file permissions for the Integration Node by web user role using 'read+:write+:execute+' , or 'all+'
    # '+' grants permission, '-' denies permission
    # e.g. define the following web user roles 'viewRole' and 'adminRole'
    #viewRole: 'read+:write-:execute-'
    #adminRole: 'all+'
    DataPermissions:
    # Set Admin Security Authorization file permissions for Record and Replay web user roles using 'read+:write+:execute+' , or 'all+'
    # '+' grants permission, '-' denies permission. Record and Replay roles also require 'read+' permission to be defined for the
    # Integration Node in the Permissions section above.
    # e.g. define the following web user roles 'dataViewer', 'dataReplayer' and 'adminRole'
    #dataViewer: 'read+:write-:execute-'
    #dataReplayer: 'read+:write-:execute-'
    #adminRole: 'all+'
    Server:
    # Set Admin Security Authorization file permissions for each named Integration Server
    # e.g. define the following web user roles 'viewRole' and 'adminRole' for Integration Server 'server01'
    #server01:
    #Permissions:
    #viewRole: 'read+:write-:execute-'
    #adminRole: 'all+'
    #DataPermissions:
    # Set Admin Security Authorization file permissions for Record and Replay web user role using 'read+:write+:execute+' , or 'all+'
    # '+' grants permission, '-' denies permission.
    # e.g. define the following web user roles 'dataViewer', 'dataReplayer' and 'adminRole'
    #dataViewer: 'read+:write-:execute-'
    #dataReplayer: 'read+:write-:execute+'
    #adminRole: 'all+'